public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.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 20:13:13 -0300	[thread overview]
Message-ID: <20080429231313.GA18231@dmt> (raw)
In-Reply-To: <4817A46B.7000302@us.ibm.com>

On Tue, Apr 29, 2008 at 05:42:51PM -0500, Anthony Liguori wrote:
> Marcelo Tosatti wrote:
> >Hi Anthony,
> >
> >How is -no-kvm-irqchip working with the patch?
> >  
> 
> Seems to work fine.  What is your expectation?

Just wondering if vcpu's are being properly awake.

> >Make sure the IO thread has SIG_IPI blocked (those are for APIC vcpu
> >initialization only).
> >  
> 
> Just so I'm clear, there's really no harm in not blocking SIG_IPI 
> because it would just be ignored by the IO thread (since the SIG_IPI 
> handler is a nop).  But yeah, we should explicitly block it.

Problem is if the IO thread _receives_ SIGIPI instead of some vcpu
thread. 

So there is potential harm in not blocking it.

> >What is the reason for this loop instead of a straight read? 
> >
> >Its alright to be interrupted by a signal.
> >  
> 
> Just general habit with QEMU.

Please don't :-)

> >>-        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.


-------------------------------------------------------------------------
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-29 23:13 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 [this message]
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
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=20080429231313.GA18231@dmt \
    --to=mtosatti@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /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