From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Heyi Guo <heyi.guo@linaro.org>,
linaro-uefi <linaro-uefi@lists.linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Peicong Li <lipeicong@huawei.com>
Subject: Re: [RFC] ArmPkg/ArmMmuLib: Add new attribute WRITE_BACK_NONSHARE
Date: Tue, 7 Nov 2017 11:30:33 +0000 [thread overview]
Message-ID: <20171107113033.kiyzdte6nhyh3nw7@bivouac.eciton.net> (raw)
In-Reply-To: <CAKv+Gu9nkVcA+XRq8He0DgKF+QD9czK+fqcrjM7coY95ScaDHw@mail.gmail.com>
On Tue, Nov 07, 2017 at 11:25:16AM +0000, Ard Biesheuvel wrote:
> >> I'd prefer the name
> >> ARM_MEMORY_REGION_ATTRIBUTE_WRITE_BACK_NONSHAREABLE but other than
> >> that, this looks sensible to me. Leif?
> >
> > And the same for NONSECURE, yes.
> > With that modification, this sounds like something absolutely required
> > in this situation.
> >
> > Does this scenario have any further implications for runtime use?
>
> I don't think so. These attributes are only used to select the
> attributes UEFI uses for its own mapping, and they should only be used
> for non-DRAM, so they shouldn't leak into the UEFI memory map in a way
> the OS would be able to notice.
Yes, that makes sense. Just wanted to double-check.
/
Leif
next prev parent reply other threads:[~2017-11-07 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 11:05 [RFC] ArmPkg/ArmMmuLib: Add new attribute WRITE_BACK_NONSHARE Heyi Guo
2017-11-07 11:08 ` Ard Biesheuvel
2017-11-07 11:23 ` Leif Lindholm
2017-11-07 11:25 ` Ard Biesheuvel
2017-11-07 11:30 ` Leif Lindholm [this message]
2017-11-07 11:37 ` Heyi Guo
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-list 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=20171107113033.kiyzdte6nhyh3nw7@bivouac.eciton.net \
--to=devel@edk2.groups.io \
/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