From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Zachary Amsden <zamsden@redhat.com>,
Chris Lalancette <clalance@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [RFC][PATCH 1/3] Introduce a workqueue to deliver PIT timer interrupts.
Date: Wed, 9 Jun 2010 11:40:22 -0300 [thread overview]
Message-ID: <20100609144022.GA9680@amt.cnet> (raw)
In-Reply-To: <4C0FA24F.60204@redhat.com>
On Wed, Jun 09, 2010 at 05:16:47PM +0300, Avi Kivity wrote:
> On 06/09/2010 04:23 PM, Marcelo Tosatti wrote:
> >
> >>Is there any chance that using a workqueue might help the problem of
> >>hrtimers firing too quickly? I wanted to return HR_NORESTART from
> >>pit_timer_fn always, then restart the hrtimer on delivery, but
> >>because of unreliable delivery, it wasn't clear how to do that.
> >>
> >>Perhaps the workqueue can be used to restart the timer instead,
> >>avoiding problems of impossibly small timeouts causing hrtimers to
> >>run amok.
> >It should be rearmed on ACK ideally. How come delivery is unreliable?
> >
> >BTW, a massive amount of hrtimers (_single_ non-tickless 32-vcpu guest
> >with LAPIC) results in:
> >
> >hrtimer: interrupt took 122448 ns
> >
> >in the host. So don't even need impossibly small timeouts :(
>
> Any idea where that came from? Even looping on vcpus, that took 4
> usec per vcpu.
The rearming of timers (that emulate LAPIC) cause the host hrtimer
interrupt handler to re-execute its "run expired timers" loop. If timing
is unfortunate, it'll have to do that several times.
next prev parent reply other threads:[~2010-06-09 14:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 17:55 [RFC][PATCH 0/3]: Fixes to IRQ routing Chris Lalancette
2010-06-08 17:55 ` [RFC][PATCH 1/3] Introduce a workqueue to deliver PIT timer interrupts Chris Lalancette
2010-06-09 2:36 ` Zachary Amsden
2010-06-09 13:23 ` Marcelo Tosatti
2010-06-09 14:16 ` Avi Kivity
2010-06-09 14:40 ` Marcelo Tosatti [this message]
2010-06-09 21:17 ` Zachary Amsden
2010-06-10 9:24 ` Avi Kivity
2010-06-10 19:17 ` Zachary Amsden
2010-06-10 16:18 ` Marcelo Tosatti
2010-06-09 10:55 ` Avi Kivity
2010-06-09 13:49 ` Marcelo Tosatti
2010-06-09 14:20 ` Avi Kivity
2010-06-08 17:55 ` [RFC][PATCH 2/3] Allow any LAPIC to accept PIC interrupts Chris Lalancette
2010-06-08 17:55 ` [RFC][PATCH 3/3] In DM_LOWEST, only deliver interrupts to vcpus with enabled LAPIC's Chris Lalancette
2010-06-09 11:01 ` Gleb Natapov
2010-06-09 11:08 ` Avi Kivity
2010-06-09 11:20 ` Gleb Natapov
2010-06-09 11:22 ` Avi Kivity
2010-06-09 11:02 ` [RFC][PATCH 0/3]: Fixes to IRQ routing Avi Kivity
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=20100609144022.GA9680@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=clalance@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=zamsden@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