From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [patch uq/master 2/4] qemu: kvm specific wait_io_event
Date: Thu, 18 Feb 2010 16:33:51 +0200 [thread overview]
Message-ID: <4B7D4FCF.907@redhat.com> (raw)
In-Reply-To: <20100218135839.GA7147@amt.cnet>
On 02/18/2010 03:58 PM, Marcelo Tosatti wrote:
> On Thu, Feb 18, 2010 at 10:29:35AM +0200, Avi Kivity wrote:
>
>>> +static void qemu_kvm_wait_io_event(CPUState *env)
>>> +{
>>> + while (!cpu_has_work(env))
>>> + qemu_cond_timedwait(env->halt_cond,&qemu_global_mutex, 1000);
>>> +
>>> + qemu_wait_io_event_common(env);
>>> }
>>>
>> Shouldn't kvm specific code be in kvm-all.c?
>>
> The context is in vl.c, so don't see much gain.
>
ok.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-02-18 14:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 22:14 [patch uq/master 0/4] uq/master: iothread consume signals via sigtimedwait and cleanups Marcelo Tosatti
2010-02-17 22:14 ` [Qemu-devel] " Marcelo Tosatti
2010-02-17 22:14 ` [patch uq/master 1/4] qemu: block SIGCHLD in vcpu thread(s) Marcelo Tosatti
2010-02-17 22:14 ` [patch uq/master 2/4] qemu: kvm specific wait_io_event Marcelo Tosatti
2010-02-17 22:14 ` [Qemu-devel] " Marcelo Tosatti
2010-02-18 8:29 ` Avi Kivity
2010-02-18 13:58 ` Marcelo Tosatti
2010-02-18 14:33 ` Avi Kivity [this message]
2010-02-17 22:14 ` [patch uq/master 3/4] qemu: kvm: consume internal signal with sigtimedwait Marcelo Tosatti
2010-02-17 22:14 ` [Qemu-devel] " Marcelo Tosatti
2010-02-17 22:14 ` [patch uq/master 4/4] qemu: kvm: remove pre-entry exit_request check with iothread enabled Marcelo Tosatti
2010-02-17 22:14 ` [Qemu-devel] " Marcelo Tosatti
2010-02-18 8:26 ` [patch uq/master 0/4] uq/master: iothread consume signals via sigtimedwait and cleanups Avi Kivity
2010-02-22 8:59 ` Avi Kivity
2010-02-22 8:59 ` [Qemu-devel] " 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=4B7D4FCF.907@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.