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: Common changes for 6.10
Date: Fri, 10 May 2024 16:50:46 -0700 [thread overview]
Message-ID: <20240510235055.2811352-2-seanjc@google.com> (raw)
In-Reply-To: <20240510235055.2811352-1-seanjc@google.com>
Nothing too exciting, a few cleanups and a fix for GUEST_MEMFD docs.
The following changes since commit fec50db7033ea478773b159e0e2efb135270e3b7:
Linux 6.9-rc3 (2024-04-07 13:22:46 -0700)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-generic-6.10
for you to fetch changes up to 2098acaf24455698c149b27f0347eb4ddc6d2058:
KVM: fix documentation for KVM_CREATE_GUEST_MEMFD (2024-05-03 15:11:23 -0700)
----------------------------------------------------------------
KVM cleanups for 6.10:
- Misc cleanups extracted from the "exit on missing userspace mapping" series,
which has been put on hold in anticipation of a "KVM Userfault" approach,
which should provide a superset of functionality.
- Remove kvm_make_all_cpus_request_except(), which got added to hack around an
AVIC bug, and then became dead code when a more robust fix came along.
- Fix a goof in the KVM_CREATE_GUEST_MEMFD documentation.
----------------------------------------------------------------
Anish Moorthy (3):
KVM: Clarify meaning of hva_to_pfn()'s 'atomic' parameter
KVM: Add function comments for __kvm_read/write_guest_page()
KVM: Simplify error handling in __gfn_to_pfn_memslot()
Carlos López (1):
KVM: fix documentation for KVM_CREATE_GUEST_MEMFD
Venkatesh Srinivas (1):
KVM: Remove kvm_make_all_cpus_request_except()
Documentation/virt/kvm/api.rst | 2 +-
include/linux/kvm_host.h | 2 --
virt/kvm/kvm_main.c | 59 +++++++++++++++++-------------------------
3 files changed, 25 insertions(+), 38 deletions(-)
next prev parent reply other threads:[~2024-05-10 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 23:50 KVM: x86 pull requests for 6.10 Sean Christopherson
2024-05-10 23:50 ` Sean Christopherson [this message]
2024-05-10 23:50 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: Selftests cleanups and fixes " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: Selftests "tree"-wide changes " Sean Christopherson
2024-05-10 23:50 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2024-05-12 7:19 ` KVM: x86 pull requests " 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=20240510235055.2811352-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