From: Dario Faggioli <raistlin@linux.it>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH v3 ]libxl: allow to set more than 31 vcpus
Date: Fri, 01 Jun 2012 12:47:44 +0200 [thread overview]
Message-ID: <1338547664.31901.54.camel@Abyss> (raw)
In-Reply-To: <1338547136.17466.77.camel@zakaz.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 2161 bytes --]
On Fri, 2012-06-01 at 11:38 +0100, Ian Campbell wrote:
> > Anyway, I just tried 25 and 33 and 65, and creation of the domain worked
> > without raising any errors! Then I double-checked, and saw that, in the
> > 'above 16' cases, Xen deliberately paused a lot of VCPUs. Also, if I log
> > into the guest /proc/cpuinfo reports only CPUs 0 and 32 (and 64 in the
> > 65 VCPUs case).
>
> All 64 online?
>
I see all of them from the host (xl vcpu-list) but a kind of random
number of them from the guest...
> It might be that the issue being fixed here only manifests on HVM. I'm
> not really sure how 64 would work otherwise since cur_vcpus in the IDL
> is definitely an int, which is what needs fixing!
>
and in fact, I agreed with that part of the patch. Also, yes, I'm trying
PV but can try HVM as well and see what happens.
> libxl__build_post is also probably buggy with max_vcpus >
> nr-bits-in(curr_vcpus) and from the looks of it it just overflows off
> the end(!), which is also fixed here...
>
What I can do is trying again with the patch applied, and if it still
behaves weird I'll go seeing what might be still missing.
> > "max. number of cpus supported by hypervisor" to be different from the
> > actual number of physical processors, and I was sort-of mislead by the
> > machine I use to test Xen every day (where that is actually happening!).
> > If it is not like that, I guess I can agree with you on this change.
>
> It's certainly supposed to be "get max. number of physical cpus", quite
> how that relates to the actual number of physical cpus I'm not sure.
>
> It's definitely not something to do with virtual cpus (for which there
> is a limit, but not this one...)
>
Ok, with that "physical" you're putting there, I see and agree it could
be useful untie it from the "virtual world". :-)
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-06-01 10:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 2:48 [PATCH v3 ]libxl: allow to set more than 31 vcpus Zhang, Yang Z
2012-06-01 6:35 ` Dario Faggioli
2012-06-01 7:18 ` Zhang, Yang Z
2012-06-01 8:44 ` Dario Faggioli
2012-06-01 8:58 ` Ian Campbell
2012-06-01 9:32 ` Dario Faggioli
2012-06-01 9:41 ` Ian Campbell
2012-06-01 10:23 ` Dario Faggioli
2012-06-01 10:38 ` Ian Campbell
2012-06-01 10:47 ` Dario Faggioli [this message]
2012-06-01 10:50 ` Ian Campbell
2012-06-01 11:04 ` Dario Faggioli
2012-06-01 11:09 ` Ian Campbell
2012-06-01 11:44 ` Ian Campbell
2012-06-22 12:11 ` Ian Campbell
2012-06-24 23:35 ` Zhang, Yang Z
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1338547664.31901.54.camel@Abyss \
--to=raistlin@linux.it \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.