From: Will Deacon <will.deacon@arm.com>
To: Catalin Marinas <Catalin.Marinas@arm.com>
Cc: "Jonathan (Zhixiong) Zhang" <zjzhang@codeaurora.org>,
"fu.wei@linaro.org" <fu.wei@linaro.org>,
"al.stone@linaro.org" <al.stone@linaro.org>,
"bp @ alien8 . de Matt Fleming" <matt.fleming@intel.com>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>
Subject: Re: [PATCH V7 3/5] arm64: mm: add PROT_DEVICE_nGnRnE and PROT_NORMAL_WT
Date: Fri, 24 Jul 2015 17:26:54 +0100 [thread overview]
Message-ID: <20150724162654.GB21177@arm.com> (raw)
In-Reply-To: <20150724161500.GV3550@e104818-lin.cambridge.arm.com>
On Fri, Jul 24, 2015 at 05:15:00PM +0100, Catalin Marinas wrote:
> On Tue, Jul 21, 2015 at 10:59:18PM +0100, Jonathan (Zhixiong) Zhang wrote:
> > *
> > * n = AttrIndx[2:0]
> > * n MAIR
> > @@ -303,12 +303,14 @@ ENTRY(__cpu_setup)
> > * DEVICE_GRE 010 00001100
> > * NORMAL_NC 011 01000100
> > * NORMAL 100 11111111
> > + * NORMAL_WT 101 10111011
>
> I don't think the write allocation hint makes much sense for WT memory
> (though it shouldn't cause issues either). Just use 10101010.
The EFI spec actually specifies the 1011 1011 encoding, so I think we should
follow that.
Will
next prev parent reply other threads:[~2015-07-24 16:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 21:59 [PATCH V7 0/5] map GHES memory region according to EFI memory map Jonathan (Zhixiong) Zhang
2015-07-21 21:59 ` [PATCH V7 1/5] efi: x86: rearrange efi_mem_attributes() Jonathan (Zhixiong) Zhang
2015-07-21 21:59 ` [PATCH V7 2/5] x86: acpi: implement arch_apei_get_mem_attributes() Jonathan (Zhixiong) Zhang
2015-07-21 21:59 ` [PATCH V7 3/5] arm64: mm: add PROT_DEVICE_nGnRnE and PROT_NORMAL_WT Jonathan (Zhixiong) Zhang
2015-07-24 2:52 ` Hanjun Guo
2015-07-24 16:15 ` Catalin Marinas
2015-07-24 16:26 ` Will Deacon [this message]
2015-07-24 16:34 ` Catalin Marinas
2015-07-24 19:02 ` Zhang, Jonathan Zhixiong
2015-07-27 10:22 ` Catalin Marinas
2015-07-21 21:59 ` [PATCH V7 4/5] arm64: apei: implement arch_apei_get_mem_attributes() Jonathan (Zhixiong) Zhang
2015-07-24 2:59 ` Hanjun Guo
2015-07-24 19:25 ` Zhang, Jonathan Zhixiong
2015-07-24 14:57 ` Will Deacon
2015-07-24 16:21 ` Catalin Marinas
2015-07-24 16:26 ` Will Deacon
2015-07-24 18:46 ` Zhang, Jonathan Zhixiong
2015-07-27 9:38 ` Matt Fleming
2015-07-27 9:45 ` Will Deacon
2015-07-27 9:54 ` Matt Fleming
2015-07-29 0:58 ` Zhang, Jonathan Zhixiong
2015-07-21 21:59 ` [PATCH V7 5/5] acpi, apei: use appropriate pgprot_t to map GHES memory Jonathan (Zhixiong) Zhang
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=20150724162654.GB21177@arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=al.stone@linaro.org \
--cc=fu.wei@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=rjw@rjwysocki.net \
--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