From: Avi Kivity <avi@qumranet.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti <marcelo@kvack.org>
Subject: Re: KVM Test result, kernel 873c05f.., userspace d102d75..
Date: Thu, 24 Apr 2008 16:44:27 +0300 [thread overview]
Message-ID: <48108EBB.3050606@qumranet.com> (raw)
In-Reply-To: <48108C08.1020706@redhat.com>
Chris Lalancette wrote:
> Avi Kivity wrote:
>
>> Ok. __pit_timer_fn() is called from an interrupt, which then calls
>> smp_call_function_single(), which calls spin_lock(). If we've already
>> taken the lock, we hang.
>>
>>
>
> Ah. Just adding a "me too"; I didn't get a chance to debug it yesterday, but I
> was seeing similar problems. If I disabled in-kernel pit with -no-kvm-pit, all
> was well.
>
How to fix it, though? the only idea that comes to mind is to affine
the hrtimer with vcpu0 (like the local apic timers) which would mean we
only need to unwait the waitqueue, and never need to send the IPI.
Would slightly improve performance as well.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-24 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 10:30 KVM Test result, kernel 873c05f.., userspace d102d75 Yunfeng Zhao
2008-04-24 11:37 ` Avi Kivity
2008-04-24 12:59 ` Yang, Sheng
2008-04-24 13:00 ` Avi Kivity
2008-04-24 13:21 ` Avi Kivity
2008-04-24 13:32 ` Chris Lalancette
2008-04-24 13:44 ` Avi Kivity [this message]
2008-04-24 16:31 ` Marcelo Tosatti
2008-04-24 16:52 ` 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=48108EBB.3050606@qumranet.com \
--to=avi@qumranet.com \
--cc=clalance@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=marcelo@kvack.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