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/
Home Products Support Community News


Re: [Xen-devel] Dom0 vCPU restriction

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Dom0 vCPU restriction
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 08 Aug 2008 09:10:27 +0100
Delivery-date: Fri, 08 Aug 2008 01:10:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <489C175C.76E4.0078.0@xxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acj5LjczdZL01WUhEd2pWwAWy6hiGQ==
Thread-topic: [Xen-devel] Dom0 vCPU restriction
User-agent: Microsoft-Entourage/
Is it useful? I guess we can support it if there is a use case.

 -- Keir

On 8/8/08 08:52, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> Is there any technical reason for restricting dom0_max_vcpus to be no
> greater than num_online_cpus()? Since Dom0's vCPU-s can be pinned
> later to a subset of physical CPUs anyway, allowing more vCPU-s from
> the beginning would seem to be only consistent.
> Thanks, Jan
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>