public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, thomas.lendacky@amd.com
Cc: Brijesh Singh <brijesh.singh@amd.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] [PATCH v2] OvmfPkg/QemuFlashFvbServicesRuntimeDxe: Use physical address with SEV-ES
Date: Tue, 26 Jan 2021 01:30:39 +0100	[thread overview]
Message-ID: <2bd3cbc9-49fa-a9fe-8551-73f3aa541583@redhat.com> (raw)
In-Reply-To: <84a5f9161541db5aa3b57c96b737afbcb4b6189d.1611410263.git.thomas.lendacky@amd.com>

On 01/23/21 14:57, Lendacky, Thomas wrote:
> From: Tom Lendacky <thomas.lendacky@amd.com>
> 
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=3183
> 
> Under SEV-ES, a write to the flash device is done using a direct VMGEXIT
> to perform an MMIO write. The address provided to the MMIO write must be
> the physical address of the MMIO write destitnation. During boot, OVMF
> runs with an identity mapped pagetable structure so that VA == PA and the
> VMGEXIT MMIO write destination is just the virtual address of the flash
> area address being written.
> 
> However, when the UEFI SetVitualAddressMap() API is invoked, an identity
> mapped pagetable structure may not be in place and using the virtual
> address for the flash area address is no longer valid. This results in
> writes to the flash not being performed successfully. This can be seen
> by attempting to change the boot order under Linux. The update will
> appear to be performed, based on the output of the command. But rebooting
> the guest will show that the new boot order has not been set.
> 
> To remedy this, save the value of the flash base physical address before
> converting the address as part of SetVirtualAddressMap(). The physical
> address can then be calculated by obtaining the offset of the MMIO target
> virtual address relative to the flash base virtual address and adding that
> to the original flash base physical address. The resulting value produces
> a successful MMIO write during runtime services.
> 
> Fixes: 437eb3f7a8db7681afe0e6064d3a8edb12abb766
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
>  .../QemuFlashDxe.c                            | 20 ++++++++++++++++++-
>  1 file changed, 19 insertions(+), 1 deletion(-)
> 
> diff --git a/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/QemuFlashDxe.c b/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/QemuFlashDxe.c
> index 1b0742967f71..d303b0078b08 100644
> --- a/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/QemuFlashDxe.c
> +++ b/OvmfPkg/QemuFlashFvbServicesRuntimeDxe/QemuFlashDxe.c
> @@ -16,11 +16,17 @@
>  
>  #include "QemuFlash.h"
>  
> +STATIC EFI_PHYSICAL_ADDRESS mSevEsFlashPhysBase;
> +
>  VOID
>  QemuFlashConvertPointers (
>    VOID
>    )
>  {
> +  if (MemEncryptSevEsIsEnabled ()) {
> +    mSevEsFlashPhysBase = (UINTN) mFlashBase;
> +  }
> +
>    EfiConvertPointer (0x0, (VOID **) &mFlashBase);
>  }
>  
> @@ -52,11 +58,23 @@ QemuFlashPtrWrite (
>    if (MemEncryptSevEsIsEnabled ()) {
>      MSR_SEV_ES_GHCB_REGISTER  Msr;
>      GHCB                      *Ghcb;
> +    EFI_PHYSICAL_ADDRESS      PhysAddr;
>      BOOLEAN                   InterruptState;
>  
>      Msr.GhcbPhysicalAddress = AsmReadMsr64 (MSR_SEV_ES_GHCB);
>      Ghcb = Msr.Ghcb;
>  
> +    //
> +    // The MMIO write needs to be to the physical address of the flash pointer.
> +    // Since this service is available as part of the EFI runtime services,
> +    // account for a non-identity mapped VA after SetVitualAddressMap().
> +    //
> +    if (mSevEsFlashPhysBase == 0) {
> +      PhysAddr = (UINTN) Ptr;
> +    } else {
> +      PhysAddr = mSevEsFlashPhysBase + (Ptr - mFlashBase);
> +    }
> +
>      //
>      // Writing to flash is emulated by the hypervisor through the use of write
>      // protection. This won't work for an SEV-ES guest because the write won't
> @@ -68,7 +86,7 @@ QemuFlashPtrWrite (
>      Ghcb->SharedBuffer[0] = Value;
>      Ghcb->SaveArea.SwScratch = (UINT64) (UINTN) Ghcb->SharedBuffer;
>      VmgSetOffsetValid (Ghcb, GhcbSwScratch);
> -    VmgExit (Ghcb, SVM_EXIT_MMIO_WRITE, (UINT64) (UINTN) Ptr, 1);
> +    VmgExit (Ghcb, SVM_EXIT_MMIO_WRITE, PhysAddr, 1);
>      VmgDone (Ghcb, InterruptState);
>    } else {
>      *Ptr = Value;
> 

Reviewed-by: Laszlo Ersek <lersek@redhat.com>

I've fixed up the typo as discussed elsewhere in this thread, in both
the commit message and the code comment.

Merged as commit 3a3501862f73, via
<https://github.com/tianocore/edk2/pull/1389>.

Thanks
Laszlo


      parent reply	other threads:[~2021-01-26  0:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-23 13:57 [PATCH v2] OvmfPkg/QemuFlashFvbServicesRuntimeDxe: Use physical address with SEV-ES Lendacky, Thomas
2021-01-23 14:02 ` Lendacky, Thomas
2021-01-25 13:55 ` Lendacky, Thomas
2021-01-25 22:17   ` Laszlo Ersek
2021-01-25 22:35     ` Lendacky, Thomas
2021-01-26  0:30 ` 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=2bd3cbc9-49fa-a9fe-8551-73f3aa541583@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