From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [PATCH] qemu-kvm: Consolidate kvm_eat_signals
Date: Mon, 12 May 2008 10:11:54 -0500 [thread overview]
Message-ID: <48285E3A.1080806@codemonkey.ws> (raw)
In-Reply-To: <48285754.5080600@qumranet.com>
Avi Kivity wrote:
>> Now the VCPU threads never select so the whole loop can be simplified
>> to a single sigtimedwait() that always blocks.
>>
>> In reality, I don't think sigtimedwait() is really needed/useful for
>> VCPUs anymore. We only use it to catch SIG_IPI and we only use
>> SIG_IPI to break out of sleeping. I don't see any reason why we
>> couldn't switch over to using a file descriptor for notification (or
>> a pthread condition).
>
> How would you stop a vcpu running in guest mode?
Yeah, I forgot about that.
>> In the very least, we could just select() on nothing and allow
>> SIG_IPI to break us out of the select.
>
> sigtimedwait() (or just sigwait, now) doesn't require the signal to be
> delivered, so it's faster.
Yeah, sigtimedwait() is probably the right thing to do since we have to
use a signal for IPI.
Regards,
Anthony Liguori
> If there's nothing to select, why call select()?
>
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2008-05-12 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 10:50 [PATCH] qemu-kvm: Consolidate kvm_eat_signals Jan Kiszka
2008-05-12 11:33 ` Avi Kivity
2008-05-12 11:42 ` Jan Kiszka
2008-05-12 11:56 ` Avi Kivity
2008-05-12 14:31 ` Anthony Liguori
2008-05-12 14:42 ` Avi Kivity
2008-05-12 15:11 ` Anthony Liguori [this message]
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=48285E3A.1080806@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=jan.kiszka@web.de \
--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