public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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 19:22:53 -0500	[thread overview]
Message-ID: <4817BBDD.4020505@us.ibm.com> (raw)
In-Reply-To: <20080430000829.GA18682@dmt>

Marcelo Tosatti wrote:
> True.
>
> Either way, this starvation due to signals can't happen with the current
> scheme because signals are blocked. It seems a significant drawback.
>   

Practically speaking, I don't see signal starving being a problem.  Part 
of the benefit of this approach is that we're reducing the overall 
number of signals received.  With the in-kernel PIT, the number of 
userspace signals is even further reduced.

> Moving the signal handling + pipe write to a separate thread should get
> rid of it.
>   

Yeah, but then you just introduce buffering problems since if you're 
getting that many signals, the pipe will get full.

No point in designing for something that isn't likely to happen in practice.

Regards,

Anthony Liguori

>> 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.
>>     
>
> I'll try to reproduce that, thanks.
>
>   
>> -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

  reply	other threads:[~2008-04-30  0:22 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
2008-04-30  0:08             ` Marcelo Tosatti
2008-04-30  0:22               ` Anthony Liguori [this message]
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=4817BBDD.4020505@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