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


Does dom0 see all physical processors? (RE: [Xen-ia64-devel] SAL INFO vi

To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Does dom0 see all physical processors? (RE: [Xen-ia64-devel] SAL INFO virtualization)
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 4 Apr 2006 10:17:32 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 03 Apr 2006 19:18:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZW7OS7i6T2NrXMSOOcInzmys000gABrI5AABDA/2AAE7wNQA==
Thread-topic: Does dom0 see all physical processors? (RE: [Xen-ia64-devel] SAL INFO virtualization)
>From: Magenheimer, Dan (HP Labs Fort Collins)
>Sent: 2006年4月3日 23:55
>> Just an unrelated comment, Dom0 should always run on every
>> processor, which is the base requirement for performance
>> reason. It's not
>> "therefore" result of this specific issue and instead you can
>> take it as the
>> basic assumption for your thought. :-)
>> Thanks,
>> Kevin
>Hmmm... are you saying that on a 16-processor Xen system,
>domain0 will run as a 16-way SMP guest?

OK, seems that I didn't describe the case clearly. :-) For current xen
model, dom0 default runs on all physical cpus which is however 

    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); /* vcpu N runs on physical cpu N */

In this case, max vcpus of dom0 is configurable but each vcpu is running 
at different physical processor once allocated. For a typical SMP box, 
such model can provide better performance or else dom0 will become the 
bottle neck if only owning one physical processor.

Then consider your question about a large box with many processors. 
How about the real environment? Is it the case to provide a 16-way SMP 
box, or a 16-way NUMA box? I prefer to the latter. If it's a NUMA box, 
dom0 sees physical ACPI table and can be configured as NUMA aware.

Yes, such binding model may change later but it's always bad to have 
dom0 only running on single physical processor.

CC to a wider list for comments. :-)


>This isn't the case today with Xen (x86 or ia64) and I
>don't expect that it will work this way in the future

Xen-ia64-devel mailing list

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