[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150615141533.GB17685@codeblueprint.co.uk>
Date: Mon, 15 Jun 2015 15:15:33 +0100
From: Matt Fleming <matt@...eblueprint.co.uk>
To: Borislav Petkov <bp@...en8.de>
Cc: "Zhang, Jonathan Zhixiong" <zjzhang@...eaurora.org>,
Matt Fleming <matt.fleming@...el.com>,
Thomas Gleixner <tglx@...utronix.de>, fu.wei@...aro.org,
al.stone@...aro.org, tony.luck@...il.com, rjw@...ysocki.net,
lenb@...nel.org, ying.huang@...el.com, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3 4/4] acpi, apei: use EFI memmap to map GHES memory
On Sat, 13 Jun, at 10:27:51AM, Borislav Petkov wrote:
> On Fri, Jun 12, 2015 at 04:44:25PM -0700, Zhang, Jonathan Zhixiong wrote:
> > Since such function is only needed for APEI functionality, at least as
> > of today, I will name it arch_apei_get_mem_attribute().
>
> Why?
>
> It can be extended to be used generically too, no? Come to think of it,
> the different arches should already have a way to tell you with what mem
> attributes a physical address is mapped, no?
>
> IOW, such functionality should be already present, you'd only have to
> find it and use it.
I did think about this, but I don't think we have a generic way to ask
the firmware for its memory map.
The problem on x86 of course is that we simply ignore what the firmware
tells us most of the time because everything gets funneled through the
e820 map and we eventually discard the EFI memmap.
--
Matt Fleming, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists