From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Matthew Hall <matt-Etm38r6YSMlqcVXhcSD7Ah2eb7JE58TQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Problem with SMP boot
Date: Sat, 27 Jan 2007 10:27:15 +0200 [thread overview]
Message-ID: <45BB0CE3.4010005@qumranet.com> (raw)
In-Reply-To: <45BA5032.6050100-Etm38r6YSMlqcVXhcSD7Ah2eb7JE58TQ@public.gmane.org>
Matthew Hall wrote:
> Avi Kivity wrote:
>
>> kvm only supports uniprocessor guests at this time.
>>
>
> Out of interest, if/when
when.
> kvm supports smp guests aswell as hosts would
> the guest be presented with a multiple virtual or physical cpu's?
> Ie. If the guest has multiple virtual cpu's the process would only run
> as a single task which would then affine to a single cpu on a multiple
> cpu host.
>
> So could kvm let an smp guest share the physical cpu's the host has?
>
kvm maps a guest vcpu to a host thread. In turn, the host scheduler
maps host threads to host cpus, so the mapping of vcpus to cpus depends
on resource availability: if you have enough cpus, the scheduler will
assign each vcpu to a separate cpu.
The user will also be able to affect the mapping by binding vcpu threads
to specific processors.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-01-27 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 22:44 Problem with SMP boot Tim Chen
[not found] ` <1169765044.30807.19.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-01-26 6:06 ` Matthew Hall
[not found] ` <45B99A66.4090406-Etm38r6YSMlqcVXhcSD7Ah2eb7JE58TQ@public.gmane.org>
2007-01-26 16:59 ` Tim Chen
2007-01-26 17:58 ` Avi Kivity
[not found] ` <45BA413F.5030307-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-26 17:54 ` Tim Chen
[not found] ` <1169834079.30807.33.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-01-27 8:40 ` Avi Kivity
2007-01-26 19:02 ` Matthew Hall
[not found] ` <45BA5032.6050100-Etm38r6YSMlqcVXhcSD7Ah2eb7JE58TQ@public.gmane.org>
2007-01-27 8:27 ` Avi Kivity [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=45BB0CE3.4010005@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=matt-Etm38r6YSMlqcVXhcSD7Ah2eb7JE58TQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox