public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Lendacky <thomas.lendacky@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Kim Phillips <kim.phillips@amd.com>,
	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>,
	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: Mon, 2 Feb 2026 10:09:19 -0600	[thread overview]
Message-ID: <3392d89c-ebf5-48f2-b498-a7dc532a0493@amd.com> (raw)
In-Reply-To: <20260202154936.GAaYDHkOMpjFpoBe5m@fat_crate.local>

On 2/2/26 09:49, Borislav Petkov wrote:
> On Mon, Feb 02, 2026 at 09:38:50AM -0600, Tom Lendacky wrote:
>> I guess it really depends on the persons point of view. I agree that
>> renaming the SNP_FEATURES_PRESENT to SNP_FEATURES_IMPL(EMENTED) would
>> match up nicely with SNP_FEATURES_IMPL_REQ. Maybe that's all that is
>> needed...
> 
> I guess...
> 
> I still think it would be useful to have a common place that says which things
> in SEV_STATUS are supported and present in a guest, no?

But I can see that getting stale because it isn't required to be updated
for features that don't require an implementation in order for the guest
to boot successfully. Whereas the SNP_FEATURES_IMPL_REQ is set with
known values that require an implementation and all the reserved bits
set. So it takes actual updating to get one of those features to work
that are represented in that bitmap.

> 
> Or are we going to dump that MSR like Joerg's patch from a while ago and
> that'll tell us what the guest supports?

That will tell us what the guest is running with, not what it can run with.

Thanks,
Tom

> 
> Hmm.
> 


  reply	other threads:[~2026-02-02 16:09 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
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 [this message]
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=3392d89c-ebf5-48f2-b498-a7dc532a0493@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=bp@alien8.de \
    --cc=david.kaplan@amd.com \
    --cc=kim.phillips@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=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