From: "David S. Ahern" <daahern@cisco.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: scheduling of qemu threads
Date: Fri, 01 Aug 2008 05:50:46 -0600 [thread overview]
Message-ID: <4892F896.4040006@cisco.com> (raw)
In-Reply-To: <4891E230.8090109@codemonkey.ws>
Anthony Liguori wrote:
> David S. Ahern wrote:
>> Last week or so Anthony made a comment about qemu basically being single
>> threaded given its global mutex. What are the impacts to simultaneous
>> scheduling of qemu threads? As I understand it, qemu has a main thread,
>> a monitor thread, an IO thread and a thread for each vcpu. Can 2 or more
>> vcpu threads run concurrently? Can a vcpu thread and an IO thread run
>> concurrently? Does kvm alter the concurrency?
>>
>
> All threads run in lock-step except when a VCPU is running (via
> kvm_run). So a VCPU can run while the IO thread is active. Only one
> VCPU can execute IO at a given time though.
Not to be dense, but do you mean yes 2 or more vcpu threads can be run
at the same time? I ask because it does not make sense for them not to
be performance wise, but at the same time following the code from
kvm_main_loop_cpu() to kvm_run() I do not see the qemu_mutex unlocked
before the ioctl(). I only see it unlocked in kvm_main_loop_wait().
thanks,
david
>
> Regards,
>
> Anthony Liguori
>
>> david
>>
>
>
prev parent reply other threads:[~2008-08-01 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 15:50 [Qemu-devel] scheduling of qemu threads David S. Ahern
2008-07-31 16:02 ` [Qemu-devel] " Anthony Liguori
2008-08-01 11:50 ` David S. Ahern [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=4892F896.4040006@cisco.com \
--to=daahern@cisco.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).