All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KVM: x86: Misc changes for 6.20
Date: Mon, 9 Feb 2026 13:19:39 -0800	[thread overview]
Message-ID: <aYpPay9AuD3KkYfr@google.com> (raw)
In-Reply-To: <CABgObfatae4rtioViKGueFG9=Qm=qEmvXQp=8LWhZnUMML7_9w@mail.gmail.com>

On Mon, Feb 09, 2026, Paolo Bonzini wrote:
> On Sat, Feb 7, 2026 at 5:10 AM Sean Christopherson <seanjc@google.com> wrote:
> >  - Add WARNs to guard against modifying KVM's CPU caps outside of the intended
> >    setup flow, as nested VMX in particular is sensitive to unexpected changes
> >    in KVM's golden configuration.
> 
> Possible follow-up: does it make sense to sync kvm_caps.supported_xss
> by calling kvm_setup_xss_caps() from kvm_finalize_cpu_caps()?

Ha!  I did that in v1[*], but Xiaoyao didn't like that it hid the XSS setup, which
very technically aren't part of kvm_cpu_caps.  For the current code base, the pros
and cons of each approach seem to largely cancel each other out, so I think my vote
is to keep things as-is for now, and revisit things if/when we end up with more
common code that needs to run right before kvm_finalize_cpu_caps().

[*] https://lore.kernel.org/all/20260123221542.2498217-2-seanjc@google.com

  reply	other threads:[~2026-02-09 21:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07  4:10 [GIT PULL] KVM: x86 pull requests for 6.20 Sean Christopherson
2026-02-07  4:10 ` [GIT PULL] KVM: x86: APIC related changes " Sean Christopherson
2026-02-09 18:33   ` Paolo Bonzini
2026-02-07  4:10 ` [GIT PULL] KVM: Generic " Sean Christopherson
2026-02-09 17:38   ` Paolo Bonzini
2026-02-09 17:42     ` Paolo Bonzini
2026-02-10  0:33       ` Sean Christopherson
2026-02-27 23:21         ` Sean Christopherson
2026-02-28 13:56           ` Paolo Bonzini
2026-03-02 14:53             ` Sean Christopherson
2026-02-07  4:10 ` [GIT PULL] KVM: guest_memfd " Sean Christopherson
2026-02-07  4:10 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2026-02-09 17:56   ` Paolo Bonzini
2026-02-09 21:19     ` Sean Christopherson [this message]
2026-02-07  4:10 ` [GIT PULL] KVM: x86: Mediated PMU " Sean Christopherson
2026-02-09 16:44   ` Sean Christopherson
2026-02-07  4:10 ` [GIT PULL] KVM: selftests changes " Sean Christopherson
2026-02-09 17:46   ` Paolo Bonzini
2026-02-07  4:10 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2026-02-09 17:51   ` Paolo Bonzini
2026-02-07  4:10 ` [GIT PULL] KVM: x86: VMX " 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=aYpPay9AuD3KkYfr@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.