From: David Woodhouse <dwmw2@infradead.org>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>, Paul Durrant <paul@xen.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Fred Griffoul <fgriffo@amazon.co.uk>
Subject: Re: [PATCH v4 00/12] KVM: x86/xen: Don't drop event deliveries which race memslot updates
Date: Wed, 04 Nov 2026 16:42:49 -0800 [thread overview]
Message-ID: <eaedfc6249d8e1e1b0418e693918e5975479220c.camel@infradead.org> (raw)
In-Reply-To: <auuNplHvOT0XL1fZ@google.com>
[-- Attachment #1: Type: text/plain, Size: 2420 bytes --]
On Wed, 2026-11-04 at 11:55 -0800, Sean Christopherson wrote:
>
> Apparently I suck extra hard at reading today. I responded to the cover letter
> with basically the same response, and _then_ I saw this. /facepalm
>
> At least we're in general agreement. I've got patch 1 earmarked, so no need to
> resend that one.
Cool. And all the atomic-SRCU stuff has landed in 7.4-rc1 too, so I no
longer have any great need to split these preliminary cleanups from the
real GPC-SRCU work. I'm inclined to send them all together, which gives
us fewer things to track — but I'm happy to do otherwise if you prefer.
I'd actually pulled in the KVM_XEN_VCPU_ATTR_TYPE_WRITE_HYPERCALL_PAGE
thing too, as the retry handling touched that. It's kind of a non-
sequitur now, but I'm keeping it in the set anyway unless you object.
The preliminary set is now:
David Woodhouse (4):
KVM: x86/xen: Fill the hypercall page with a single guest write
KVM: x86/xen: Add KVM_XEN_VCPU_ATTR_TYPE_WRITE_HYPERCALL_PAGE
KVM: x86: Request the guest TLB flush from record_steal_time()
KVM: selftests: Actually deactivate the HVA-based shared_info cache in xen_shinfo_test
Sean Christopherson (3):
KVM: x86/xen: Extract delivery of event to vCPU into a separate helper
KVM: x86/xen: Explicitly tag "shared info" page as never being dirty tracked
KVM: x86/xen: Don't dirty track "vCPU info" page
Followed by the actual GPC conversion to atomic-SRCU:
Carsten Stollmaier (1):
KVM: x86: Use gfn_to_pfn_cache for steal time / preempted status
David Woodhouse (9):
KVM: pfncache: Use atomic SRCU for readers instead of a rwlock
KVM: pfncache: Add guest-mode pinning (GUEST_USES_PFN successor)
KVM: x86: Post KVM_REQ_GET_NESTED_STATE_PAGES on memslot updates
KVM: nSVM: Use a gfn_to_pfn_cache for the vmcb12 page
KVM: nSVM: Cache L1's MSR permissions map pages
KVM: nSVM: Cache L1's IO permissions map pages
KVM: selftests: Add nested transition benchmark
KVM: selftests: Add Xen evtchn vs memslot-update race test
KVM: selftests: Add Xen evtchn vs mmu_notifier race test for HVA caches
Fred Griffoul (3):
KVM: nVMX: Implement cache for L1 MSR bitmap
KVM: nVMX: Use pinned pfncache for L1 APIC virtualization pages
KVM: selftests: Add nested VMX APIC cache invalidation test
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6179 bytes --]
next prev parent reply other threads:[~2026-11-05 0:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 16:24 David Woodhouse
2026-10-19 16:24 ` [PATCH v4 01/12] KVM: x86/xen: Don't block memslot updates while halted in SCHEDOP_poll David Woodhouse
2026-10-19 16:24 ` [PATCH v4 02/12] KVM: pfncache: Return -EAGAIN for a lookup which hits an invalid memslot David Woodhouse
2026-10-19 16:24 ` [PATCH v4 03/12] KVM: pfncache: Add a 'wait' argument to the refresh and activate functions David Woodhouse
2026-10-19 16:24 ` [PATCH v4 04/12] KVM: x86/xen: Wait out memslot updates in the Xen attribute ioctls David Woodhouse
2026-10-19 16:24 ` [PATCH v4 05/12] KVM: x86/xen: Don't lose the timer event when delivery fails transiently David Woodhouse
2026-10-19 16:24 ` [PATCH v4 06/12] KVM: x86/xen: Retry event channel delivery which races a memslot update David Woodhouse
2026-10-19 16:24 ` [PATCH v4 07/12] KVM: x86/xen: Extract delivery of event to vCPU into a separate helper David Woodhouse
2026-10-19 16:24 ` [PATCH v4 08/12] KVM: x86/xen: Explicitly tag "shared info" page as never being dirty tracked David Woodhouse
2026-10-19 16:24 ` [PATCH v4 09/12] KVM: x86/xen: Don't dirty track "vCPU info" page David Woodhouse
2026-10-19 16:24 ` [PATCH v4 10/12] KVM: x86: Request the guest TLB flush from record_steal_time() David Woodhouse
2026-10-19 16:24 ` [PATCH v4 11/12] KVM: selftests: Add Xen evtchn vs memslot-update race test David Woodhouse
2026-10-19 16:24 ` [PATCH v4 12/12] KVM: selftests: Fix unreachable timer recovery in xen_shinfo_test David Woodhouse
2026-11-03 22:46 ` [PATCH v4 00/12] KVM: x86/xen: Don't drop event deliveries which race memslot updates David Woodhouse
2026-11-04 19:55 ` Sean Christopherson
2026-11-05 0:42 ` David Woodhouse [this message]
2026-11-04 19:53 ` 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=eaedfc6249d8e1e1b0418e693918e5975479220c.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=fgriffo@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@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®