mirror of https://lore.kernel.org/lkml/
 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,
	 Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: Generic changes for 6.13
Date: Tue, 12 Nov 2024 11:33:31 -0800	[thread overview]
Message-ID: <20241112193335.597514-2-seanjc@google.com> (raw)
In-Reply-To: <20241112193335.597514-1-seanjc@google.com>

Please pull two changes that coincidentally happen to be related to vcpu->pid.

The following changes since commit 5cb1659f412041e4780f2e8ee49b2e03728a2ba6:

  Merge branch 'kvm-no-struct-page' into HEAD (2024-10-25 13:38:16 -0400)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-generic-6.13

for you to fetch changes up to 3e7f43188ee227bcf0f07f60a00f1fd1aca10e6a:

  KVM: Protect vCPU's "last run PID" with rwlock, not RCU (2024-10-30 14:41:22 -0700)

----------------------------------------------------------------
KVM generic changes for 6.13

 - Rework kvm_vcpu_on_spin() to use a single for-loop instead of making two
   partial poasses over "all" vCPUs.  Opportunistically expand the comment
   to better explain the motivation and logic.

 - Protect vcpu->pid accesses outside of vcpu->mutex with a rwlock instead
   of RCU, so that running a vCPU on a different task doesn't encounter
   long stalls due to having to wait for all CPUs become quiescent.

----------------------------------------------------------------
Sean Christopherson (3):
      KVM: Rework core loop of kvm_vcpu_on_spin() to use a single for-loop
      KVM: Return '0' directly when there's no task to yield to
      KVM: Protect vCPU's "last run PID" with rwlock, not RCU

 arch/arm64/include/asm/kvm_host.h |   2 +-
 include/linux/kvm_host.h          |   3 +-
 virt/kvm/kvm_main.c               | 143 ++++++++++++++++++++++----------------
 3 files changed, 86 insertions(+), 62 deletions(-)

  reply	other threads:[~2024-11-12 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 19:33 [GIT PULL] KVM: x86 " Sean Christopherson
2024-11-12 19:33 ` Sean Christopherson [this message]
2024-11-12 19:33 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2024-11-13 11:52   ` Paolo Bonzini
2024-11-12 19:33 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2024-11-12 19:33 ` [GIT PULL] KVM: Selftests " Sean Christopherson
2024-11-12 19:33 ` [GIT PULL] KVM: VMX change " Sean Christopherson
2024-11-13 12:23 ` [GIT PULL] KVM: x86 changes " Paolo Bonzini

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=20241112193335.597514-2-seanjc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®