From: Laszlo Ersek <lersek@redhat.com>
To: Brijesh Singh <brijesh.singh@amd.com>, edk2-devel@lists.01.org
Cc: Lendacky Thomas <Thomas.Lendacky@amd.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Anthony Perard <anthony.perard@citrix.com>,
Julien Grall <julien.grall@linaro.org>,
Justen Jordan L <jordan.l.justen@intel.com>
Subject: Re: [PATCH v4 0/3] OvmfPkg: mark flash memory range as MMIO
Date: Fri, 6 Jul 2018 20:48:40 +0200 [thread overview]
Message-ID: <80de9c9a-0c63-25a1-e79b-22ea0ff26fc0@redhat.com> (raw)
In-Reply-To: <1530889242-21667-1-git-send-email-brijesh.singh@amd.com>
On 07/06/18 17:00, Brijesh Singh wrote:
> The Qemu flash range is marked as 'system ram' in EFI runtime memmap
> but it is actually an IO address. The patch series updates the
> EFI runtime memmap to add this range as Memory Mapped IO address.
>
> Changes since v3:
> - minor changes to address Laszlo's review feedback.
>
> Changes since v2:
> - added cover letter and extend CC list to add all OvmfPkg
> maintainers/reviewers.
>
> Changes since v1:
> - split the OvmfPkg single patch into three patches based on Laszlo's feedback.
> a) mark memory as MMIO for non SEV case
> b) do not adding EFI runtime mapping for SMM build
> c) clear C-bit when SEV is active for non SMM builds only
>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Anthony Perard <anthony.perard@citrix.com>
> Cc: Julien Grall <julien.grall@linaro.org>
> Cc: Justen Jordan L <jordan.l.justen@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
>
> Complete tree is available:
> url: https://github.com/codomania/edk2.git
> branch: qemu-flash-mmio-v4
>
> Brijesh Singh (3):
> OvmfPkg/QemuFlashFvbServicesRuntimeDxe: mark Flash memory range as
> MMIO
> OvmfPkg/QemuFlashFvbServicesRuntimeDxe: Do not expose MMIO in SMM
> build
> OvmfPkg/QemuFlashFvbServicesRuntimeDxe: Restore C-bit when SEV is
> active
>
> .../FvbServicesRuntimeDxe.inf | 1 +
> .../FwBlockService.c | 38 +-----------
> .../FwBlockService.h | 7 +++
> .../FwBlockServiceDxe.c | 67 ++++++++++++++++++++++
> .../FwBlockServiceSmm.c | 13 +++++
> 5 files changed, 89 insertions(+), 37 deletions(-)
>
series
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Regression-tested-by: Laszlo Ersek <lersek@redhat.com>
Commit range 9090c8b53301..75b7aa9528bd.
Thank you for the contribution! The first two patches are a good general
improvement for non-SEV guests as well.
Laszlo
prev parent reply other threads:[~2018-07-06 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 15:00 [PATCH v4 0/3] OvmfPkg: mark flash memory range as MMIO Brijesh Singh
2018-07-06 15:00 ` [PATCH v4 1/3] OvmfPkg/QemuFlashFvbServicesRuntimeDxe: mark Flash " Brijesh Singh
2018-07-06 15:00 ` [PATCH v4 2/3] OvmfPkg/QemuFlashFvbServicesRuntimeDxe: Do not expose MMIO in SMM build Brijesh Singh
2018-07-06 15:00 ` [PATCH v4 3/3] OvmfPkg/QemuFlashFvbServicesRuntimeDxe: Restore C-bit when SEV is active Brijesh Singh
2018-07-06 18:48 ` Laszlo Ersek [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=80de9c9a-0c63-25a1-e79b-22ea0ff26fc0@redhat.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