[PATCH 10/12] kexec: arrange for paddr_vmcoreinfo_note() to return phys_addr_t
bhe at redhat.com
Tue May 3 02:01:20 PDT 2016
On 05/03/16 at 11:23am, Pratyush Anand wrote:
> Hi Baoquan,
> On 03/05/2016:12:24:41 PM, Baoquan He wrote:
> > Hi Pratyush,
> > Could you please help tell why arm PAE kernel can be put above 4G?
> PAE system can have physical addresses above 4G. So, if a CPU is supporting the
> LPAE page table format then we should be able to access physical addresses
> beyond 4G.
OK, after patient explanation from Pratush on irc, I finally understand on
arm LPAE there's PHYS_OFFSET which indicats the physical address of main
memory since arm could map some amount of device memory to cpu address space
below 4G. Then physical ram has to be started from above 4G form cpu
point of view. That's why kernel need be put above 4G. It's fair enough to
fix it in this patch. Certainly if this explanation is also added into
patch log, non arm developer will understand the change better.
> > Since the change is related to common code, I am curious about how
> > it's so different with other ARCHs.
> paddr_vmcoreinfo_note() returns a physical address, so returning phys_addr_t
> seems most appropriate. So, kernel variable may land into above 4G locations,
> even with the platform in other architecture (with PAE support), if start of RAM
> is located very high,
> So, in my opinion it would be safer to have these changes for other ARCHs as
> kexec mailing list
> kexec at lists.infradead.org
More information about the kexec