[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Setting dom0-cpus to 0 doesn't use all cpus asdocumented

To: "Ryan Harper" <ryanh@xxxxxxxxxx>
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 9 May 2006 16:52:53 +0100
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx, "Krysan, Susan" <KRYSANS@xxxxxxxxxx>, "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>, "Carb, Brian A" <Brian.Carb@xxxxxxxxxx>
Delivery-date: Tue, 09 May 2006 08:53:24 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AcZzf48YnVAkwqGRT7mabYMwoPUEdQAAPrQA
Thread-topic: [Xen-devel] Setting dom0-cpus to 0 doesn't use all cpus asdocumented

 
> > You can just use the normal xm commands to vary the number of CPUs.
> > Restarting xend is a rather brutal way of trying to achieve 
> the same 
> > thing...
> 
> Is it worth keeping dom0-cpus then?

Yes, it sets it when xend starts.

Ian

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

Follow-Ups:
- RE: [Xen-devel] Setting dom0-cpus to 0 doesn't use all cpus asdocumented
  - From: Jan Beulich

Prev by Date: [Xen-devel] Re: [RFC PATCH 15/35] subarch support for controlling interrupt delivery
Next by Date: RE: [Xen-devel] Setting dom0-cpus to 0 doesn't use all cpus asdocumented
Previous by thread: Re: [Xen-devel] Setting dom0-cpus to 0 doesn't use all cpus asdocumented
Next by thread: RE: [Xen-devel] Setting dom0-cpus to 0 doesn't use all cpus asdocumented
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.