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.19
Date: Tue, 25 Nov 2025 17:44:48 -0800 [thread overview]
Message-ID: <20251126014455.788131-2-seanjc@google.com> (raw)
In-Reply-To: <20251126014455.788131-1-seanjc@google.com>
A tweak to account for an upcoming API change, and a doc fix.
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-generic-6.19
for you to fetch changes up to 04fd067b770d19fee39759d994c4bfa2fb332d9f:
KVM: Fix VM exit code for full dirty ring in API documentation (2025-10-14 15:19:05 -0700)
----------------------------------------------------------------
KVM generic changes for 6.19:
- Use the recently-added WQ_PERCPU when creating the per-CPU workqueue for
irqfd cleanup.
- Fix a goof in the dirty ring documentation.
----------------------------------------------------------------
Leonardo Bras (1):
KVM: Fix VM exit code for full dirty ring in API documentation
Marco Crivellari (1):
KVM: Explicitly allocate/setup irqfd cleanup as per-CPU workqueue
Documentation/virt/kvm/api.rst | 2 +-
virt/kvm/eventfd.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
next prev parent reply other threads:[~2025-11-26 1:45 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 ` Sean Christopherson [this message]
2025-11-26 8:59 ` [GIT PULL] KVM: Generic changes for 6.19 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
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=20251126014455.788131-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