From: Ingo Molnar <mingo@kernel.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: linux-coco@lists.linux.dev, kvm@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] x86/sev/vc: fix efi runtime instruction emulation
Date: Thu, 26 Jun 2025 10:21:15 +0200 [thread overview]
Message-ID: <aF0C-wVwXWxFjgud@gmail.com> (raw)
In-Reply-To: <20250626074236.307848-2-kraxel@redhat.com>
* Gerd Hoffmann <kraxel@redhat.com> wrote:
> In case efi_mm is active go use the userspace instruction decoder which
> supports fetching instructions from active_mm. This is needed to make
> instruction emulation work for EFI runtime code, so it can use cpuid
> and rdmsr.
>
> EFI runtime code uses the cpuid instruction to gather information about
> the environment it is running in, such as SEV being enabled or not, and
> choose (if needed) the SEV code path for ioport access.
>
> EFI runtime code uses the rdmsr instruction to get the location of the
> CAA page (see SVSM spec, section 4.2 - "Post Boot").
>
> The big picture behind this is that the kernel needs to be able to
> properly handle #VC exceptions that come from EFI runtime services.
> Since EFI runtime services have a special page table mapping for the EFI
> virtual address space, the efi_mm context must be used when decoding
> instructions during #VC handling.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> arch/x86/coco/sev/vc-handle.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/coco/sev/vc-handle.c b/arch/x86/coco/sev/vc-handle.c
> index 0989d98da130..e498a8965939 100644
> --- a/arch/x86/coco/sev/vc-handle.c
> +++ b/arch/x86/coco/sev/vc-handle.c
> @@ -17,6 +17,7 @@
> #include <linux/mm.h>
> #include <linux/io.h>
> #include <linux/psp-sev.h>
> +#include <linux/efi.h>
> #include <uapi/linux/sev-guest.h>
>
> #include <asm/init.h>
> @@ -178,9 +179,14 @@ static enum es_result __vc_decode_kern_insn(struct es_em_ctxt *ctxt)
> return ES_OK;
> }
>
> +/*
> + * User instruction decoding is also required for the EFI runtime. Even though
> + * EFI runtime is running in kernel mode, it uses special EFI virtual address
s/Even though EFI runtime
/Even though the EFI runtime
> + * mappings that require the use of efi_mm to properly address and decode.
> + */
> static enum es_result vc_decode_insn(struct es_em_ctxt *ctxt)
> {
> - if (user_mode(ctxt->regs))
> + if (user_mode(ctxt->regs) || current->active_mm == &efi_mm)
Instead of open-coding that condition, we have mm_is_efi() for that.
Thanks,
Ingo
next prev parent reply other threads:[~2025-06-26 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 7:42 [PATCH v3 0/2] x86/sev: improve efi runtime code support Gerd Hoffmann
2025-06-26 7:42 ` [PATCH v3 1/2] x86/sev/vc: fix efi runtime instruction emulation Gerd Hoffmann
2025-06-26 8:21 ` Ingo Molnar [this message]
2025-06-26 7:42 ` [PATCH v3 2/2] x86/sev: Let sev_es_efi_map_ghcbs() map the caa pages too Gerd Hoffmann
2025-06-26 8:19 ` Ingo Molnar
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=aF0C-wVwXWxFjgud@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).