From: Kim Phillips <kim.phillips@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
<linux-coco@lists.linux.dev>, <x86@kernel.org>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Nikunj A Dadhania <nikunj@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Michael Roth <michael.roth@amd.com>,
Naveen Rao <naveen.rao@amd.com>,
David Kaplan <david.kaplan@amd.com>, <stable@kernel.org>
Subject: Re: [PATCH 1/2] KVM: SEV: IBPB-on-Entry guest support
Date: Thu, 29 Jan 2026 16:32:49 -0600 [thread overview]
Message-ID: <f42e878a-d56f-413d-87e1-19acdc6de690@amd.com> (raw)
In-Reply-To: <20260129105116.GBaXs7pBF-k4x_5_W1@fat_crate.local>
On 1/29/26 4:51 AM, Borislav Petkov wrote:
> On Wed, Jan 28, 2026 at 06:38:29PM -0600, Kim Phillips wrote:
>> SNP_FEATURES_PRESENT is for the non-trivial variety: Its bits get set as
>> part of the patchseries that add the explicit guest support *code*.
> Yes, and I'm asking why can't SNP_FEATURES_PRESENT contain *all* SNP features?
Not *all* SNP features are implemented in all guest kernel versions, and,
well, for those that don't require explicit guest code support, perhaps it's
because they aren't necessarily well defined and validated in all hardware
versions...
Kim
next prev parent reply other threads:[~2026-01-29 22:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 22:42 [PATCH 0/2] KVM: SEV: Add support for IBPB-on-Entry Kim Phillips
2026-01-26 22:42 ` [PATCH 1/2] KVM: SEV: IBPB-on-Entry guest support Kim Phillips
2026-01-27 6:19 ` Nikunj A. Dadhania
2026-01-28 19:02 ` Tom Lendacky
2026-01-28 19:23 ` Borislav Petkov
2026-01-29 0:38 ` Kim Phillips
2026-01-29 10:51 ` Borislav Petkov
2026-01-29 22:32 ` Kim Phillips [this message]
2026-01-30 12:32 ` Borislav Petkov
2026-01-30 14:56 ` Tom Lendacky
2026-01-30 15:45 ` Borislav Petkov
2026-02-02 15:38 ` Tom Lendacky
2026-02-02 15:49 ` Borislav Petkov
2026-02-02 16:09 ` Tom Lendacky
2026-02-02 17:12 ` Borislav Petkov
2026-01-26 22:42 ` [PATCH 2/2] KVM: SEV: Add support for IBPB-on-Entry Kim Phillips
2026-01-27 6:38 ` Nikunj A. Dadhania
2026-01-27 20:56 ` Kim Phillips
2026-01-28 19:08 ` Tom Lendacky
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=f42e878a-d56f-413d-87e1-19acdc6de690@amd.com \
--to=kim.phillips@amd.com \
--cc=bp@alien8.de \
--cc=david.kaplan@amd.com \
--cc=kprateek.nayak@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=naveen.rao@amd.com \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=stable@kernel.org \
--cc=thomas.lendacky@amd.com \
--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