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: x86 pull requests for 7.2
Date: Thu, 11 Jun 2026 17:47:45 -0700 [thread overview]
Message-ID: <20260612004755.349925-1-seanjc@google.com> (raw)
Sorry for not getting these to you yesterday. I was all prepared to work on
them before meetings hit, and then SQUIRREL!
Outside of these pull requests, there's a set of five selftests patches[1] that
I have sitting in "selftests_l2_stacks" and fed into linux-next. I'm not
including a pull request for that branch, as it's deliberately built on top of
all the other local merges to avoid a pile of annoying conflicts (the changes
allocate a proper stack for all L2 vCPUs, and so touches every test that does
anything nested related). If you can apply the patches directly after merging
the other pull requests, that would make me quite happy. Alternatively, I'll
send a separate pull request once this batch is merged.
[1] https://lore.kernel.org/all/20260610003030.2957261-1-seanjc@google.com
There are two conflicts I am aware of; thankfully both are fairly trivial.
Internal to these pull requests, "misc" and "svm" conflict on header includes
in svm.h: take the incoming headers and the kvm_cache_regs.h => regs.h rename.
diff --cc arch/x86/kvm/svm/svm.h
index d013a5ceb62e,87c6b105deef..000000000000
--- a/arch/x86/kvm/svm/svm.h
+++ b/arch/x86/kvm/svm/svm.h
@@@ -23,7 -23,9 +23,9 @@@
#include <asm/sev-common.h>
#include "cpuid.h"
-#include "kvm_cache_regs.h"
+#include "regs.h"
+ #include "x86.h"
+ #include "pmu.h"
/*
* Helpers to convert to/from physical addresses for pages whose address is
Externally, the "mmu" branch will conflict with the tip tree on
arch/x86/include/asm/tdx.h. Mark's fixup in -next[2] is what I've been using
in my local resolutions. Basically take the KVM changes, but keep the
void tdx_sys_disable(void); declaration.
[2] https://lore.kernel.org/all/ahb-PZwR5mEd8A9W@sirena.org.uk
next reply other threads:[~2026-06-12 0:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 0:47 Sean Christopherson [this message]
2026-06-12 0:47 ` [GIT PULL] KVM: x86: Generic changes " Sean Christopherson
2026-06-12 8:07 ` Paolo Bonzini
2026-06-12 0:47 ` [GIT PULL] KVM: x86: guest_memfd " Sean Christopherson
2026-06-12 8:10 ` Paolo Bonzini
2026-06-12 0:47 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2026-06-12 8:14 ` Paolo Bonzini
2026-06-12 0:47 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2026-06-12 8:14 ` Paolo Bonzini
2026-06-12 0:47 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2026-06-12 8:12 ` Paolo Bonzini
2026-06-12 0:47 ` [GIT PULL] KVM: x86: SEV " Sean Christopherson
2026-06-12 8:13 ` Paolo Bonzini
2026-06-12 0:47 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2026-06-12 0:47 ` [GIT PULL] KVM: VFIO " Sean Christopherson
2026-06-12 8:14 ` Paolo Bonzini
2026-06-12 0:47 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2026-06-12 8:15 ` 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=20260612004755.349925-1-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®