WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Vcpu allocation for a newly created domU

To: Sandesh <sandesh.ahiremath@xxxxxxxxx>
Subject: Re: [Xen-devel] Vcpu allocation for a newly created domU
From: "Grzegorz Miłoś" <gm281@xxxxxxxxx>
Date: Wed, 18 Jun 2008 17:09:55 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 18 Jun 2008 09:10:16 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=wQ4sTt0cg85Qh1DmLfnv1oZKtVxii0ok3b2oXwic4U8=; b=hSIfF7zybBBT69H4pdjOWqLyG47kwLc/gIb2e1eGZiCMViBrYCFv4ierEufyn3u+e9 HsSGwderAXZJfkSMnbkwcUurZV4WqCMeUFpTDRtyJ1QnP32377m9+VbX6JCmTSYIA7ov +4vkNy0jOdruaPcw5z/IIRmEhydVR1tPIJ6n0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=K2iYwZ5eFFskfxVoxbTi+eNGor3vyaDB53HqAlN9TIUxv0Ic/QOFJX9fUzYLeL8R0+ kWhr+oDtaV5xzSGs5Em37XBhY327trdN2BvX1C0PgLwXql7BufDNBzq//AvrZB3ilVbv Vddx6jB+NqNKvIYug0ltjgbVj4byDreIMixMo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1213790518.4439.72.camel@ec4t16cg-1518809>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1213636037.4215.39.camel@ec4t16cg-1518809> <4cac40570806180413j59d3ca82hcc42d34d62ad1192@xxxxxxxxxxxxxx> <1213790518.4439.72.camel@ec4t16cg-1518809>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> > 1. So how will dom0 relinquish/share vcpu to/with a newly created domU.
>> > Does this happen as part of the shared_info page mapping??
>>
>> vcpus are created for each new domain, they are not shared with Dom0.
> in xen/arch/x86/setup.c right after domain_create(0,0, DOM0_SSIDREF)
> which creates dom0, alloc_vcpu(dom0..) is called which will allocate
> vcpu for dom0. Then in construct_dom0 alloc_vcpu is called for
> dom0_max_cpus. So aren't all vcpu's getting allocated to dom0??
>
> Or is it that domU will get allocated separate vcpu's, irrespective of
> these above vcpu's??

Each domain, Dom0 and any DomU, will get separate VCPU(s). These are
dynamically bound/run on physical CPUs.

Cheers
Gr(z)egor(z)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel