From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Laszlo Ersek <lersek@redhat.com>
Cc: Michael Zimmermann <sigmaepsilon92@gmail.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 0/2] ArmVirtPkg/HighMemDxe: fix issues reported by Michael
Date: Tue, 21 Mar 2017 10:42:41 +0000 [thread overview]
Message-ID: <CAKv+Gu8=7vnFm3U0P0zEBg+tW=MJA3EeSAqhKzwtpunCPXnfeg@mail.gmail.com> (raw)
In-Reply-To: <1490088209-8564-1-git-send-email-ard.biesheuvel@linaro.org>
On 21 March 2017 at 09:23, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> This fixes two separate issues reported by Michael:
> - setting EFI_MEMORY_XP via the GCD memory space map always fails,
> - patchable PCD updates do not propagate to other modules.
>
> Ard Biesheuvel (2):
> ArmVirtPkg/HighMemDxe: use CPU arch protocol to apply memprotect
> policy
> ArmVirtPkg/HighMemDxe: check new regions against GCD memory space map
>
> ArmVirtPkg/HighMemDxe/HighMemDxe.c | 59 ++++++++++++++------
> ArmVirtPkg/HighMemDxe/HighMemDxe.inf | 2 +-
> 2 files changed, 43 insertions(+), 18 deletions(-)
>
Pushed as
60bd1e1269ff ArmVirtPkg/HighMemDxe: use CPU arch protocol to apply
memprotect policy
5d5a19028a55 ArmVirtPkg/HighMemDxe: check new regions against GCD
memory space map
Thanks,
prev parent reply other threads:[~2017-03-21 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 9:23 [PATCH 0/2] ArmVirtPkg/HighMemDxe: fix issues reported by Michael Ard Biesheuvel
2017-03-21 9:23 ` [PATCH 1/2] ArmVirtPkg/HighMemDxe: use CPU arch protocol to apply memprotect policy Ard Biesheuvel
2017-03-21 10:36 ` Laszlo Ersek
2017-03-21 9:23 ` [PATCH 2/2] ArmVirtPkg/HighMemDxe: check new regions against GCD memory space map Ard Biesheuvel
2017-03-21 10:40 ` Laszlo Ersek
2017-03-21 10:42 ` Ard Biesheuvel [this message]
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='CAKv+Gu8=7vnFm3U0P0zEBg+tW=MJA3EeSAqhKzwtpunCPXnfeg@mail.gmail.com' \
--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