[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180716122623.GB7160@dhcp-128-65.nay.redhat.com>
Date: Mon, 16 Jul 2018 20:26:23 +0800
From: Dave Young <dyoung@...hat.com>
To: AKASHI Takahiro <takahiro.akashi@...aro.org>
Cc: catalin.marinas@....com, will.deacon@....com, dhowells@...hat.com,
vgoyal@...hat.com, herbert@...dor.apana.org.au,
davem@...emloft.net, bhe@...hat.com, arnd@...db.de,
ard.biesheuvel@...aro.org, james.morse@....com,
bhsharma@...hat.com, kexec@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH v11 03/15] powerpc, kexec_file: factor out memblock-based
arch_kexec_walk_mem()
Hi Akashi,
On 07/11/18 at 04:41pm, AKASHI Takahiro wrote:
> Memblock list is another source for usable system memory layout.
> So powerpc's arch_kexec_walk_mem() is moved to kexec_file.c so that
> other memblock-based architectures, particularly arm64, can also utilise
> it. A moved function is now renamed to kexec_walk_memblock() and merged
> into the existing arch_kexec_walk_mem() for general use, either resource
> list or memblock list.
>
> A consequent function will not work for kdump with memblock list, but
> this will be fixed in the next patch.
If this breaks something, then it would be good to fold the following
patch in this patch so that bisect can still work?
Thanks
Dave
Powered by blists - more mailing lists