From: Matt Fleming <matt@codeblueprint.co.uk>
To: Borislav Petkov <bp@alien8.de>
Cc: "Zhang, Jonathan Zhixiong" <zjzhang@codeaurora.org>,
Matt Fleming <matt.fleming@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
fu.wei@linaro.org, al.stone@linaro.org, tony.luck@gmail.com,
rjw@rjwysocki.net, lenb@kernel.org, ying.huang@intel.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 4/4] acpi, apei: use EFI memmap to map GHES memory
Date: Mon, 15 Jun 2015 15:15:33 +0100 [thread overview]
Message-ID: <20150615141533.GB17685@codeblueprint.co.uk> (raw)
In-Reply-To: <20150613082750.GA3470@pd.tnic>
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
next prev parent reply other threads:[~2015-06-15 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 18:25 [PATCH V3 0/4] map GHES memory region with EFI memory map Jonathan (Zhixiong) Zhang
2015-06-11 18:26 ` [PATCH V3 4/4] acpi, apei: use EFI memmap to map GHES memory Jonathan (Zhixiong) Zhang
2015-06-12 16:29 ` Borislav Petkov
2015-06-12 23:44 ` Zhang, Jonathan Zhixiong
2015-06-13 8:27 ` Borislav Petkov
2015-06-15 14:15 ` Matt Fleming [this message]
2015-06-15 14:59 ` Borislav Petkov
2015-06-22 5:11 ` Matt Fleming
2015-06-23 9:50 ` Matt Fleming
[not found] <E1ZG8Pn-0002uB-2C@feisty.vs19.net>
2015-07-21 0:22 ` Zhang, Jonathan Zhixiong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150615141533.GB17685@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=al.stone@linaro.org \
--cc=bp@alien8.de \
--cc=fu.wei@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=tony.luck@gmail.com \
--cc=ying.huang@intel.com \
--cc=zjzhang@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).