From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Peter Meier <meiepeter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Host/Guest SMP: Looking for answers
Date: Tue, 24 Jul 2007 16:59:06 +0300 [thread overview]
Message-ID: <46A605AA.8030809@qumranet.com> (raw)
In-Reply-To: <c354edc90707240636m33417598qb541125784ffb55f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Peter Meier wrote:
> Hello,
>
> I've heard that KVM-33 now supports SMP hosts and SMP guests,
> which is cool. However I do have some newbie-level questions
> about this one.
>
> - I assume this is implemented by using n threads for n CPUs/CPU
> cores and letting the host OS schedule accordingly? Or does the
> VM somehow automagically bind each of its virtual CPU threads
> to one of the host CPUs/cores?
>
Every virtual cpu (vcpu) is mapped to a thread. The scheduler maps
threads to cores. It's no different than running a normal multithreaded
application.
> - I'd be interested to learn how to actually use SMP ;-). What
> options do I need to enable inside the guest kernel's menucon-
> fig beyond the basic SMP one, specifically what SMP sub-archi-
> tecture type?
>
Er, whichever you like. At present, NUMA won't buy you anything, but
that will change one day. In general any smp-enabled kernel should
work, and there's no reason to enable any fancy features.
> - For that matter, which Processor Family option is appropriate
> inside KVM? I've been using "Pentium III" so far. Should I be
> using the family of the host system?
>
P3 is a good choice, and so is using the host system. I doubt it makes
any measurable difference.
> - How do I tell the VM to use multiple CPUs/cores? Some command
> line arguments to qemu-system-x86_64, or another way?
>
Use the -smp N option as documented in the qemu help.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-07-24 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 13:36 Host/Guest SMP: Looking for answers Peter Meier
[not found] ` <c354edc90707240636m33417598qb541125784ffb55f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-24 13:59 ` Avi Kivity [this message]
[not found] ` <46A605AA.8030809-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-24 14:05 ` Peter Meier
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=46A605AA.8030809@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=meiepeter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.