From: Avi Kivity <avi@redhat.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: kvm@vger.kernel.org
Subject: Re: 0.11: SMP guests using one host CPU only?
Date: Tue, 20 Oct 2009 22:21:34 +0900 [thread overview]
Message-ID: <4ADDB95E.6080309@redhat.com> (raw)
In-Reply-To: <4ADDB8F0.5010709@wpkg.org>
On 10/20/2009 10:19 PM, Tomasz Chmielewski wrote:
>>
>> I meant, how many qemu threads are there, and how much cpu does each
>> take?
>
>
> There is only one qemu thread for the 4-cpu guest.
Not possible. Even a single-cpu guest has two threads.
What does 'ls /proc/$(pgrep qemu)/task' show?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-10-20 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 9:03 0.11: SMP guests using one host CPU only? Tomasz Chmielewski
2009-10-20 9:41 ` Avi Kivity
2009-10-20 10:17 ` Tomasz Chmielewski
2009-10-20 13:16 ` Avi Kivity
2009-10-20 13:19 ` Tomasz Chmielewski
2009-10-20 13:21 ` Avi Kivity [this message]
2009-10-20 13:48 ` Tomasz Chmielewski
2009-10-22 7:05 ` Avi Kivity
2009-10-22 9:28 ` Tomasz Chmielewski
2009-10-22 10:51 ` 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=4ADDB95E.6080309@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mangoo@wpkg.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).