From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
Rik van Riel <riel@redhat.com>,
Steven Rostedt <srostedt@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
kvm@vger.kernel.org
Subject: Re: [patch -rt 0/2] use simple waitqueue for kvm vcpu waitqueue (v3)
Date: Wed, 14 Jan 2015 18:35:27 +0100 [thread overview]
Message-ID: <54B6A8DF.3070806@redhat.com> (raw)
In-Reply-To: <20150114171251.882318257@redhat.com>
On 14/01/2015 18:12, Marcelo Tosatti wrote:
> Against v3.14-rt branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
>
> The problem:
>
> On -RT, an emulated LAPIC timer instance has the following path:
>
> 1) hard interrupt
> 2) ksoftirqd is scheduled
> 3) ksoftirqd wakes up vcpu thread
> 4) vcpu thread is scheduled
>
> This extra context switch introduces unnecessary latency in the
> LAPIC path for a KVM guest.
>
> The solution:
>
> Allow waking up vcpu thread from hardirq context,
> thus avoiding the need for ksoftirqd to be scheduled.
>
> Normal waitqueues make use of spinlocks, which on -RT
> are sleepable locks. Therefore, waking up a waitqueue
> waiter involves locking a sleeping lock, which
> is not allowed from hard interrupt context.
>
> cyclictest command line:
> # cyclictest -m -n -q -p99 -l 1000000 -h60 -D 1m
>
> This patch reduces the average latency in my tests from 14us to 11us.
>
> v2: improve changelog (Rik van Riel)
> v3: limit (once) guest triggered printk and WARN_ON (Paolo Bonzini)
>
>
Looks good.
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
prev parent reply other threads:[~2015-01-14 17:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 17:12 [patch -rt 0/2] use simple waitqueue for kvm vcpu waitqueue (v3) Marcelo Tosatti
2015-01-14 17:12 ` [patch -rt 1/2] KVM: use simple waitqueue for vcpu->wq Marcelo Tosatti
2015-01-14 18:22 ` Rik van Riel
2015-01-16 16:48 ` Steven Rostedt
2015-01-16 16:56 ` Steven Rostedt
2015-01-17 7:57 ` Peter Zijlstra
2015-01-19 14:41 ` Marcelo Tosatti
2015-01-20 5:46 ` Paul Mackerras
2015-01-20 18:16 ` Steven Rostedt
2015-01-21 15:07 ` Peter Zijlstra
2015-02-17 17:44 ` Sebastian Andrzej Siewior
2015-02-18 14:03 ` Peter Zijlstra
2015-02-25 21:02 ` Sebastian Andrzej Siewior
2015-08-07 10:57 ` Peter Zijlstra
2015-08-07 11:14 ` Peter Zijlstra
2015-08-07 16:41 ` Christoph Hellwig
2015-08-07 16:45 ` Peter Zijlstra
2015-08-09 6:39 ` Christoph Hellwig
2015-08-17 20:31 ` Thomas Gleixner
2015-02-27 0:23 ` Marcelo Tosatti
2015-03-05 1:09 ` Marcelo Tosatti
2015-03-05 7:42 ` Sebastian Andrzej Siewior
2015-03-06 13:54 ` Sebastian Andrzej Siewior
2015-01-14 17:12 ` [patch -rt 2/2] KVM: lapic: mark LAPIC timer handler as irqsafe Marcelo Tosatti
2015-01-14 18:23 ` Rik van Riel
2015-01-14 17:35 ` Paolo Bonzini [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=54B6A8DF.3070806@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=riel@redhat.com \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
/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).