From: Sean Christopherson <seanjc@google.com>
To: Jethro Beekman <jethro@fortanix.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-coco@lists.linux.dev
Subject: Re: [PATCH] KVM: SEV: Track SNP launch state and disallow invalid userspace interactions
Date: Wed, 25 Feb 2026 12:05:16 -0800 [thread overview]
Message-ID: <aZ9V_O5SGGKa-Vdn@google.com> (raw)
In-Reply-To: <d98692e2-d96b-4c36-8089-4bc1e5cc3d57@fortanix.com>
On Mon, Jan 19, 2026, Jethro Beekman wrote:
> Calling any of the SNP_LAUNCH_ ioctls after SNP_LAUNCH_FINISH results in a
> kernel page fault due to RMP violation. Track SNP launch state and exit early.
What exactly trips the RMP #PF? A backtrace would be especially helpful for
posterity.
I ask because it's basically impossible to determine if this approach is optimal
without knowing exactly what's going wrong. Semantically it sounds reasonable,
but ideally KVM would naturally handle userspace stupidity (without exploding).
next prev parent reply other threads:[~2026-02-25 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 19:06 [PATCH] KVM: SEV: Track SNP launch state and disallow invalid userspace interactions Jethro Beekman
2026-01-19 19:12 ` Jethro Beekman
2026-02-25 20:05 ` Sean Christopherson [this message]
2026-02-25 20:13 ` Jethro Beekman
2026-02-25 20:21 ` Sean Christopherson
2026-02-25 20:30 ` Jethro Beekman
2026-02-26 19:30 ` Sean Christopherson
2026-03-07 1:51 ` Sean Christopherson
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=aZ9V_O5SGGKa-Vdn@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jethro@fortanix.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@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