From: Anthony Liguori <aliguori@us.ibm.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH][RFC] Use pipe() to simulate signalfd()
Date: Tue, 29 Apr 2008 18:44:29 -0500 [thread overview]
Message-ID: <4817B2DD.7030100@us.ibm.com> (raw)
In-Reply-To: <20080429233717.GA18425@dmt>
Marcelo Tosatti wrote:
> Why? If you leave data in the pipe the next select() won't block.
>
> Isnt there the possibility that this loop can be stuck for significant
> amounts of time? If you're receiving lots of notifications through
> signals.
>
If you're getting that many signals, then select() is never going to
run anyway.
>>>>>> - kvm_eat_signal(&io_signal_table, NULL, 1000);
>>>>>> pthread_mutex_lock(&qemu_mutex);
>>>>>> - cpu_single_env = NULL;
>>>>>> - main_loop_wait(0);
>>>>>> + main_loop_wait(10);
>>>>>>
>>>>>>
>>>>>>
>>>>> Increase that 1000 or something. Will make it easier to spot bugs.
>>>>>
>>>>>
>>>>>
>>>> I have actually and it does introduce some bugs. I'm not entirely clear
>>>> what is causing them though.
>>>>
>>>>
>>> Should indicate that some event previously delivered through signals and
>>> received by sigtimedwait is not waking up the IO thread.
>>>
>>>
>> I'll take a look and see. I'm having time keeping issues in the guest
>> so it's hard to tell what problems are caused by the IO thread verses time.
>>
>
> Time issues only with the patch? If not, please share details.
>
No, they're independent of the patch. The symptom is that the guest
tends to hang during boot for prolonged periods of time. It tends to be
random whether it will hang at all, how long it will hang, and at what
point it will hang. It tends to hang more often in particular places.
In my ubuntu server guest, for instance, it tends to hang right after
partition probing, right after "Loading hardware drivers", and right
before spawning a getty on /dev/tty0.
Normally, it will only hang for a few seconds. However, with -smp N
where N > number of cpus in the host, it tends to happen more
frequently. Using clock=jiffies in the guest makes the problem go away.
-no-kvm-pit doesn't make a difference (the guest is normally using the
pm-timer).
Regards,
Anthony Liguori
-------------------------------------------------------------------------
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-29 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 14:28 [PATCH][RFC] Use pipe() to simulate signalfd() Anthony Liguori
2008-04-29 22:37 ` Marcelo Tosatti
2008-04-29 22:42 ` Anthony Liguori
2008-04-29 23:13 ` Marcelo Tosatti
2008-04-29 23:15 ` Anthony Liguori
2008-04-29 23:37 ` Marcelo Tosatti
2008-04-29 23:44 ` Anthony Liguori [this message]
2008-04-30 0:08 ` Marcelo Tosatti
2008-04-30 0:22 ` Anthony Liguori
2008-04-30 0:38 ` Marcelo Tosatti
2008-04-30 0:47 ` Anthony Liguori
2008-04-30 2:16 ` Marcelo Tosatti
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=4817B2DD.7030100@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=mtosatti@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