Re: [PATCH v26 0/7] arm64: add kdump support

On 10/18/2016 09:26 AM, AKASHI Takahiro wrote: Ruslan, On Mon, Oct 17, 2016 at 06:41:01PM +0300, Ruslan Bilovol wrote: Hi, On 09/07/2016 07:29 AM, AKASHI Takahiro wrote: v26-specific note: After a comment from Rob[0], an idea of adding "linux,usable-memory-range" was dropped.

Re: [PATCH v26 0/7] arm64: add kdump support

Ruslan, On Mon, Oct 17, 2016 at 06:41:01PM +0300, Ruslan Bilovol wrote: > Hi, > > On 09/07/2016 07:29 AM, AKASHI Takahiro wrote: > > v26-specific note: After a comment from Rob[0], an idea of adding > > "linux,usable-memory-range" was dropped. Instead, an existing > >

Re: [PATCH v26 0/7] arm64: add kdump support

Hi, On 09/07/2016 07:29 AM, AKASHI Takahiro wrote: v26-specific note: After a comment from Rob[0], an idea of adding "linux,usable-memory-range" was dropped. Instead, an existing "reserved-memory" node will be used to limit usable memory ranges on crash dump kernel.

Re: [PATCH v26 0/7] arm64: add kdump support

Manish, On Tue, Oct 04, 2016 at 06:53:28PM +0530, Manish Jaggi wrote: > > On 10/04/2016 04:23 PM, James Morse wrote: > > Hi Manish, > > > > On 04/10/16 11:05, Manish Jaggi wrote: > >> On 10/04/2016 03:16 PM, James Morse wrote: > >>> On 03/10/16 13:41, Manish Jaggi wrote: > On 10/03/2016

Re: [PATCH v26 0/7] arm64: add kdump support

On Tue, Oct 04, 2016 at 10:46:27AM +0100, James Morse wrote: > Hi Manish, > > On 03/10/16 13:41, Manish Jaggi wrote: > > On 10/03/2016 04:34 PM, AKASHI Takahiro wrote: > >> On Mon, Oct 03, 2016 at 01:24:34PM +0530, Manish Jaggi wrote: > >>> With the v26 kdump and v3 kexec-tools and top of tree

Re: [PATCH v26 0/7] arm64: add kdump support

On 10/04/2016 04:23 PM, James Morse wrote: > Hi Manish, > > On 04/10/16 11:05, Manish Jaggi wrote: >> On 10/04/2016 03:16 PM, James Morse wrote: >>> On 03/10/16 13:41, Manish Jaggi wrote: On 10/03/2016 04:34 PM, AKASHI Takahiro wrote: > On Mon, Oct 03, 2016 at 01:24:34PM +0530, Manish

Re: [PATCH v26 0/7] arm64: add kdump support

On Mon, Oct 03, 2016 at 06:11:40PM +0530, Manish Jaggi wrote: > On 10/03/2016 04:34 PM, AKASHI Takahiro wrote: > > On Mon, Oct 03, 2016 at 01:24:34PM +0530, Manish Jaggi wrote: > >> Observations: > >> 1.1. Dump capture kernel shows different memory map. > >>

Re: [PATCH v26 0/7] arm64: add kdump support

On 10/04/2016 03:16 PM, James Morse wrote: > Hi Manish, > > On 03/10/16 13:41, Manish Jaggi wrote: >> On 10/03/2016 04:34 PM, AKASHI Takahiro wrote: >>> On Mon, Oct 03, 2016 at 01:24:34PM +0530, Manish Jaggi wrote: With the v26 kdump and v3 kexec-tools and top of tree crash.git, below are

Re: [PATCH v26 0/7] arm64: add kdump support

Hi Manish, On 03/10/16 13:41, Manish Jaggi wrote: > On 10/03/2016 04:34 PM, AKASHI Takahiro wrote: >> On Mon, Oct 03, 2016 at 01:24:34PM +0530, Manish Jaggi wrote: >>> With the v26 kdump and v3 kexec-tools and top of tree crash.git, below are >>> the tests done >>> Attached is a patch in

Re: [PATCH v26 0/7] arm64: add kdump support

On Mon, Oct 03, 2016 at 06:11:40PM +0530, Manish Jaggi wrote: > > > On 10/03/2016 04:34 PM, AKASHI Takahiro wrote: > > Manish, > > > > On Mon, Oct 03, 2016 at 01:24:34PM +0530, Manish Jaggi wrote: > >> Hi Akashi, > >> > >> On 09/07/2016 09:59 AM, AKASHI Takahiro wrote: > >>> v26-specific

Re: [PATCH v26 0/7] arm64: add kdump support

Manish, On Mon, Oct 03, 2016 at 01:24:34PM +0530, Manish Jaggi wrote: > Hi Akashi, > > On 09/07/2016 09:59 AM, AKASHI Takahiro wrote: > > v26-specific note: After a comment from Rob[0], an idea of adding > > "linux,usable-memory-range" was dropped. Instead, an existing > >

Re: [PATCH v26 0/7] arm64: add kdump support

Hi Akashi, On 09/07/2016 09:59 AM, AKASHI Takahiro wrote: > v26-specific note: After a comment from Rob[0], an idea of adding > "linux,usable-memory-range" was dropped. Instead, an existing > "reserved-memory" node will be used to limit usable memory ranges > on crash dump kernel.

Re: [PATCH v26 0/7] arm64: add kdump support

On Mon, Sep 19, 2016 at 05:05:48PM +0100, James Morse wrote: > On 16/09/16 21:17, Ard Biesheuvel wrote: > > On 16 September 2016 at 17:04, James Morse wrote: > >> Mark, Ard, how does/will reserved-memory work on an APCI only system? > > > > It works by accident, at the

Re: [PATCH v26 0/7] arm64: add kdump support

James, On Fri, Sep 16, 2016 at 05:04:34PM +0100, James Morse wrote: > (Cc: Ard), > > Mark, Ard, how does/will reserved-memory work on an APCI only system? > > > On 07/09/16 05:29, AKASHI Takahiro wrote: > > v26-specific note: After a comment from Rob[0], an idea of adding > >

Re: [PATCH v26 0/7] arm64: add kdump support

On 19 September 2016 at 17:05, James Morse wrote: > On 16/09/16 21:17, Ard Biesheuvel wrote: >> On 16 September 2016 at 17:04, James Morse wrote: >>> Mark, Ard, how does/will reserved-memory work on an APCI only system? >> >> It works by accident, at the

Re: [PATCH v26 0/7] arm64: add kdump support

On 16/09/16 21:17, Ard Biesheuvel wrote: > On 16 September 2016 at 17:04, James Morse wrote: >> Mark, Ard, how does/will reserved-memory work on an APCI only system? > > It works by accident, at the moment. We used to ignore both > /memreserve/s and the /reserved-memory

Re: [PATCH v26 0/7] arm64: add kdump support

On 16 September 2016 at 17:04, James Morse wrote: > (Cc: Ard), > > Mark, Ard, how does/will reserved-memory work on an APCI only system? > It works by accident, at the moment. We used to ignore both /memreserve/s and the /reserved-memory node, but due to some unrelated

Re: [PATCH v26 0/7] arm64: add kdump support

(Cc: Ard), Mark, Ard, how does/will reserved-memory work on an APCI only system? On 07/09/16 05:29, AKASHI Takahiro wrote: > v26-specific note: After a comment from Rob[0], an idea of adding > "linux,usable-memory-range" was dropped. Instead, an existing > "reserved-memory" node

Re: [PATCH v26 0/7] arm64: add kdump support

On Wed, Sep 07, 2016 at 01:29:02PM +0900, AKASHI Takahiro wrote: > v26-specific note: After a comment from Rob[0], an idea of adding > "linux,usable-memory-range" was dropped. Instead, an existing > "reserved-memory" node will be used to limit usable memory ranges > on crash dump