From: Sean Christopherson <seanjc@google.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: kvm@vger.kernel.org, Paul Durrant <paul@xen.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Michal Luczaj <mhal@rbox.co>
Subject: Re: [PATCH v2 0/8] KVM: x86/xen updates
Date: Thu, 29 Feb 2024 15:12:49 -0800 [thread overview]
Message-ID: <ZeEPcYL0pc0zJQKZ@google.com> (raw)
In-Reply-To: <20240227115648.3104-1-dwmw2@infradead.org>
On Tue, Feb 27, 2024, David Woodhouse wrote:
> David Woodhouse (6):
> KVM: x86/xen: improve accuracy of Xen timers
> KVM: x86/xen: inject vCPU upcall vector when local APIC is enabled
> KVM: x86/xen: remove WARN_ON_ONCE() with false positives in evtchn delivery
> KVM: pfncache: simplify locking and make more self-contained
> KVM: x86/xen: fix recursive deadlock in timer injection
> KVM: pfncache: clean up rwlock abuse
>
> Paul Durrant (2):
> KVM: x86/xen: split up kvm_xen_set_evtchn_fast()
> KVM: x86/xen: avoid blocking in hardirq context in kvm_xen_set_evtchn_fast()
>
> arch/x86/kvm/lapic.c | 5 +-
> arch/x86/kvm/x86.c | 61 +++++++++-
> arch/x86/kvm/x86.h | 1 +
> arch/x86/kvm/xen.c | 327 +++++++++++++++++++++++++++++++++------------------
> arch/x86/kvm/xen.h | 18 +++
> virt/kvm/pfncache.c | 216 +++++++++++++++++-----------------
> 6 files changed, 403 insertions(+), 225 deletions(-)
FYI, I'm planning on grabbing at least the first 3 for 6.9, but I'm off tomorrow
and don't want to risk having to fix breakage in -next, so it won't happen until
next week.
I might also grab 4 and 5, I just need to stare at that locking code a bit.
next prev parent reply other threads:[~2024-02-29 23:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 11:49 [PATCH v2 0/8] KVM: x86/xen updates David Woodhouse
2024-02-27 11:49 ` [PATCH v2 1/8] KVM: x86/xen: improve accuracy of Xen timers David Woodhouse
2024-03-04 23:44 ` Sean Christopherson
2024-03-05 9:29 ` Paul Durrant
2024-03-05 21:12 ` Sean Christopherson
2024-03-06 9:48 ` Paul Durrant
2024-03-06 9:57 ` David Woodhouse
2024-02-27 11:49 ` [PATCH v2 2/8] KVM: x86/xen: inject vCPU upcall vector when local APIC is enabled David Woodhouse
2024-02-27 11:49 ` [PATCH v2 3/8] KVM: x86/xen: remove WARN_ON_ONCE() with false positives in evtchn delivery David Woodhouse
2024-02-27 11:49 ` [PATCH v2 4/8] KVM: pfncache: simplify locking and make more self-contained David Woodhouse
2024-03-05 0:08 ` Sean Christopherson
2024-02-27 11:49 ` [PATCH v2 5/8] KVM: x86/xen: fix recursive deadlock in timer injection David Woodhouse
2024-02-27 11:49 ` [PATCH v2 6/8] KVM: x86/xen: split up kvm_xen_set_evtchn_fast() David Woodhouse
2024-02-27 11:49 ` [PATCH v2 7/8] KVM: x86/xen: avoid blocking in hardirq context in kvm_xen_set_evtchn_fast() David Woodhouse
2024-02-27 14:43 ` Steven Rostedt
2024-02-27 17:00 ` David Woodhouse
2024-02-27 17:18 ` Thomas Gleixner
2024-02-27 17:22 ` David Woodhouse
2024-03-07 9:27 ` David Woodhouse
2024-03-07 10:02 ` David Woodhouse
2024-02-27 17:25 ` Steven Rostedt
2024-02-27 17:28 ` David Woodhouse
2024-03-08 18:10 ` David Woodhouse
2024-02-27 11:49 ` [PATCH v2 8/8] KVM: pfncache: clean up rwlock abuse David Woodhouse
2024-02-29 23:12 ` Sean Christopherson [this message]
2024-03-05 0:35 ` [PATCH v2 0/8] KVM: x86/xen updates 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=ZeEPcYL0pc0zJQKZ@google.com \
--to=seanjc@google.com \
--cc=dwmw2@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=paul@xen.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;
as well as URLs for NNTP newsgroup(s).