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: VMX changes for 6.19
Date: Wed, 26 Nov 2025 05:42:00 -0800	[thread overview]
Message-ID: <aScDqIjHMGHJBQ7M@google.com> (raw)
In-Reply-To: <CABgObfbvYC9mGL8x1JSQwmq7BT9j7gwf11nmHsumOumd4P0abg@mail.gmail.com>

On Wed, Nov 26, 2025, Paolo Bonzini wrote:
> On Wed, Nov 26, 2025 at 2:45 AM Sean Christopherson <seanjc@google.com> wrote:
> >
> > The highlight is EPTP construction cleanup that's worthwhile on its own, but
> > is also a step toward eliding the EPT flushes that KVM does on pCPU migration,
> > which are especially costly when running nested:
> >
> > https://lore.kernel.org/all/aJKW9gTeyh0-pvcg@google.com
> >
> > The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
> >
> >   Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
> >
> > are available in the Git repository at:
> >
> >   https://github.com/kvm-x86/linux.git tags/kvm-x86-vmx-6.19
> >
> > for you to fetch changes up to dfd1572a64c90770a2bddfab9bbb69932217b1da:
> >
> >   KVM: VMX: Make loaded_vmcs_clear() static in vmx.c (2025-11-11 07:41:16 -0800)
> 
> Pulled; there was another minor conflict due to the introduction of
> kvm_request_l1tf_flush_l1d().

Shoot, sorry, forgot about that one (obviously).

      reply	other threads:[~2025-11-26 13:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  1:44 [GIT PULL] KVM: x86 pull requests 6.19 Sean Christopherson
2025-11-26  1:44 ` [GIT PULL] KVM: Generic changes for 6.19 Sean Christopherson
2025-11-26  8:59   ` Paolo Bonzini
2025-11-26  1:44 ` [GIT PULL] KVM: guest_memfd: NUMA support and other " Sean Christopherson
2025-11-26  8:33   ` Paolo Bonzini
2025-11-26  1:44 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2025-11-26  8:49   ` Paolo Bonzini
2025-11-26  1:44 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2025-11-26  8:50   ` Paolo Bonzini
2025-11-26  1:44 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2025-11-26  8:51   ` Paolo Bonzini
2025-11-26  1:44 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-11-26  8:48   ` Paolo Bonzini
2025-11-26 13:41     ` Sean Christopherson
2025-11-26  1:44 ` [GIT PULL] KVM: x86: TDX " Sean Christopherson
2025-11-26  8:51   ` Paolo Bonzini
2025-11-26  1:44 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2025-11-26  8:50   ` Paolo Bonzini
2025-11-26 13:42     ` Sean Christopherson [this message]

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=aScDqIjHMGHJBQ7M@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.