From: David Woodhouse <dwmw2@infradead.org>
To: paul@xen.org, kvm <kvm@vger.kernel.org>
Cc: Sean Christopherson <seanjc@google.com>,
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, "Griffoul,
Fred" <fgriffo@amazon.com>
Subject: Re: [PATCH] KVM: x86: Use fast path for Xen timer delivery
Date: Fri, 22 Sep 2023 10:29:25 +0100 [thread overview]
Message-ID: <e16f0d326d4c6976a9cd194faa66e5eaf8b0c47d.camel@infradead.org> (raw)
In-Reply-To: <dff1ad07-8649-4916-bbc1-ab5cc403bb89@xen.org>
[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]
On Fri, 2023-09-22 at 10:22 +0100, Paul Durrant wrote:
> On 22/09/2023 10:20, David Woodhouse wrote:
> > From: David Woodhouse <dwmw@amazon.co.uk>
> >
> > Most of the time there's no need to kick the vCPU and deliver the timer
> > event through kvm_xen_inject_timer_irqs(). Use kvm_xen_set_evtchn_fast()
> > directly from the timer callback, and only fall back to the slow path
> > when it's necessary to do so.
> >
> > This gives a significant improvement in timer latency testing (using
> > nanosleep() for various periods and then measuring the actual time
> > elapsed).
> >
> > Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> > ---
> > arch/x86/kvm/xen.c | 17 ++++++++++++++---
> > 1 file changed, 14 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/x86/kvm/xen.c b/arch/x86/kvm/xen.c
> > index 40edf4d1974c..66c4cf93a55c 100644
> > --- a/arch/x86/kvm/xen.c
> > +++ b/arch/x86/kvm/xen.c
> > @@ -134,12 +134,23 @@ static enum hrtimer_restart xen_timer_callback(struct hrtimer *timer)
> > {
> > struct kvm_vcpu *vcpu = container_of(timer, struct kvm_vcpu,
> > arch.xen.timer);
> > + struct kvm_xen_evtchn e;
> > + int rc;
> > +
> > if (atomic_read(&vcpu->arch.xen.timer_pending))
> > return HRTIMER_NORESTART;
> >
> > - atomic_inc(&vcpu->arch.xen.timer_pending);
> > - kvm_make_request(KVM_REQ_UNBLOCK, vcpu);
> > - kvm_vcpu_kick(vcpu);
> > + e.vcpu_id = vcpu->vcpu_id;
> > + e.vcpu_idx = vcpu->vcpu_idx;
> > + e.port = vcpu->arch.xen.timer_virq;
>
> Don't you need to check the port for validity? The VMM may not have set
> it (and hence be delivering timer VIRQ events itself).
Nah, the kvm_xen_timer_enabled() check which gates all the kernel
interception of timer hypercalls is already testing precisely that.
If the TIMER_VIRQ isn't set, none of this code runs. And when userspace
tears down TIMER_VIRQ, the hrtimer is cancelled. So none of this code
(then) runs.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2023-09-22 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 9:20 David Woodhouse
2023-09-22 9:22 ` Paul Durrant
2023-09-22 9:29 ` David Woodhouse [this message]
2023-09-22 9:41 ` Paul Durrant
2023-09-27 6:42 ` David Woodhouse
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=e16f0d326d4c6976a9cd194faa66e5eaf8b0c47d.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fgriffo@amazon.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®