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-changelog

[Xen-changelog] Add 'dom0_max_vcpus' Xen boot parameter.

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] Add 'dom0_max_vcpus' Xen boot parameter.
From: Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 08 Feb 2006 18:36:10 +0000
Delivery-date: Wed, 08 Feb 2006 18:48:12 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID 6ba371536f5cbc2f0973c0e86881fec337828638
# Parent  a3d554557d48ab302eb07a1bcca975d61f0ceac2
Add 'dom0_max_vcpus' Xen boot parameter.

Signed-off-by: Keir Fraser <keir@xxxxxxxxxxxxx>

diff -r a3d554557d48 -r 6ba371536f5c xen/arch/x86/domain_build.c
--- a/xen/arch/x86/domain_build.c       Wed Feb  8 16:24:29 2006
+++ b/xen/arch/x86/domain_build.c       Wed Feb  8 16:25:14 2006
@@ -50,10 +50,13 @@
 }
 custom_param("dom0_mem", parse_dom0_mem);
 
-static unsigned int opt_dom0_shadow = 0;
+static unsigned int opt_dom0_max_vcpus;
+integer_param("dom0_max_vcpus", opt_dom0_max_vcpus);
+
+static unsigned int opt_dom0_shadow;
 boolean_param("dom0_shadow", opt_dom0_shadow);
 
-static unsigned int opt_dom0_translate = 0;
+static unsigned int opt_dom0_translate;
 boolean_param("dom0_translate", opt_dom0_translate);
 
 static char opt_dom0_ioports_disable[200] = "";
@@ -594,7 +597,13 @@
     for ( i = 0; i < MAX_VIRT_CPUS; i++ )
         d->shared_info->vcpu_info[i].evtchn_upcall_mask = 1;
 
-    for ( i = 1; i < num_online_cpus(); i++ )
+    if ( opt_dom0_max_vcpus == 0 )
+        opt_dom0_max_vcpus = num_online_cpus();
+    if ( opt_dom0_max_vcpus > MAX_VIRT_CPUS )
+        opt_dom0_max_vcpus = MAX_VIRT_CPUS;
+    printk("Dom0 has maximum %u VCPUs\n", opt_dom0_max_vcpus);
+
+    for ( i = 1; i < opt_dom0_max_vcpus; i++ )
         (void)alloc_vcpu(d, i, i);
 
     /* Set up monitor table */

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] Add 'dom0_max_vcpus' Xen boot parameter., Xen patchbot -unstable <=