From: David Woodhouse <dwmw2@infradead.org>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm <kvm@vger.kernel.org>, Paul Durrant <paul@xen.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] KVM: x86: Use fast path for Xen timer delivery
Date: Tue, 06 Feb 2024 20:36:12 -0800 [thread overview]
Message-ID: <3078fde54d6a4a34587cc14b286d7ad199e77dca.camel@infradead.org> (raw)
In-Reply-To: <ZcMG6NA63MqOR1V9@google.com>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
On Tue, 2024-02-06 at 20:28 -0800, Sean Christopherson wrote:
>
> I agree that's the long term solution, but I am not entirely confident that a big
> overhaul is 6.9 material at this point. Squeezing an overhaul into 6.8 (and if
> we're being nitpicky, backporting to 6.7) is out of the question.
It actually ends up being really simple. We just lift ->refresh_lock up
and use it to protect all the activate/deactivate/refresh paths.
I have a patch in my tree; just need to put it through some testing.
(Currently stuck in a hotel room with a bunch of positive COVID tests,
unstable wifi and no decent screen, getting a bit fractious :)
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
prev parent reply other threads:[~2024-02-07 4:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 13:58 David Woodhouse
2023-10-02 10:35 ` Paul Durrant
2023-10-02 17:00 ` Sean Christopherson
2023-10-02 17:05 ` David Woodhouse
2023-10-05 1:29 ` Sean Christopherson
2024-02-06 18:41 ` Sean Christopherson
2024-02-06 18:51 ` David Woodhouse
2024-02-07 2:58 ` Sean Christopherson
2024-02-07 3:29 ` David Woodhouse
2024-02-07 4:28 ` Sean Christopherson
2024-02-07 4:36 ` David Woodhouse [this message]
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=3078fde54d6a4a34587cc14b286d7ad199e77dca.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®