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: Tue, 23 Jun 2015 10:50:33 +0100 [thread overview]
Message-ID: <20150623095033.GC2815@codeblueprint.co.uk> (raw)
In-Reply-To: <20150622051131.GA2815@codeblueprint.co.uk>
On Mon, 22 Jun, at 06:11:31AM, Matt Fleming wrote:
>
> Right, but see my previous comment about x86 discarding a bunch of
> attributes for memory regions because the kernel "knows better".
>
> And in most places, yes, the kernel really does know better. But this
> APEI case is special because irrespective of what the kernel says we
> want to be compatible with the firmware's memory map.
>
> And we don't have an API for that.
Maybe what we want is a new PAGE_* protection that is compatible with
any firmware mappings? That'd be nice because we wouldn't have to
introduce a whole new API for this GHES case and ioremap_* could do
whatever it wanted under the hood.
Thougts?
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-06-23 9:50 UTC|newest]
Thread overview: 16+ 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:25 ` [PATCH V3 1/4] x86: acpi: define uncached page flag Jonathan (Zhixiong) Zhang
2015-06-12 7:52 ` Ingo Molnar
2015-06-12 23:49 ` Zhang, Jonathan Zhixiong
2015-06-11 18:25 ` [PATCH V3 2/4] arm64: " Jonathan (Zhixiong) Zhang
2015-06-11 18:25 ` [PATCH V3 3/4] efi: x86: rearrange efi_mem_attributes() 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
2015-06-15 14:59 ` Borislav Petkov
2015-06-22 5:11 ` Matt Fleming
2015-06-22 5:11 ` Matt Fleming
2015-06-23 9:50 ` Matt Fleming [this message]
[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=20150623095033.GC2815@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.