 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] Dom0 vCPU restriction
| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] Dom0 vCPU restriction |
| From: | "Jan Beulich" <jbeulich@xxxxxxxxxx> |
| Date: | Fri, 08 Aug 2008 08:52:28 +0100 |
| Delivery-date: | Fri, 08 Aug 2008 00:52:03 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| 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 |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] Re: Allow compile with CONFIG_DEBUG_INFO=y, X86_PAE not set on gcc 3.4.5, Simon Horman |
|---|---|
| Next by Date: | Re: [Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu, Keir Fraser |
| Previous by Thread: | [Xen-ia64-devel] [IA64] Weekly benchmark results [ww31], KUWAMURA Shin'ya |
| Next by Thread: | Re: [Xen-devel] Dom0 vCPU restriction, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
