xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com,
	Martin Lukasik <martin.lukasik@cancer.org.uk>
Subject: Re: Xen CPU limit?
Date: Tue, 30 Mar 2010 09:56:06 +0100	[thread overview]
Message-ID: <4BB1D8C60200007800037C33@vpn.id2.novell.com> (raw)
In-Reply-To: <20100330075306.GY1878@reaktio.net>

>>> Pasi Kärkkäinen<pasik@iki.fi> 30.03.10 09:53 >>>
>On Tue, Mar 30, 2010 at 08:16:26AM +0100, Jan Beulich wrote:
>> >>> Pasi Kärkkäinen<pasik@iki.fi> 29.03.10 17:49 >>>
>> >I think the number of virtual cpus (vcpus) per guest is (was) 32,
>> >and now in Xen 4.0.0 you can have up to 64 vcpus per guest.
>> 
>> I don't think the tools are up to anything beyond 32 yet. 
>
>Hmm.. what's actually missing from the tools to handle >32 vcpus?

Any place referencing XEN_LEGACY_MAX_VCPUS needs revisiting
(seems like the one obvious place that needs fixing is in
xc_domain_restore()). Beyond that I really don't know - I just know
too little about the tools.

Jan

  reply	other threads:[~2010-03-30  8:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 16:08 Xen CPU limit? Martin Lukasik
2010-03-29 15:49 ` Pasi Kärkkäinen
2010-03-30  7:16   ` Jan Beulich
2010-03-30  7:53     ` Pasi Kärkkäinen
2010-03-30  8:56       ` Jan Beulich [this message]
2010-03-30 16:14       ` Dan Magenheimer
2010-03-31  7:11         ` Jan Beulich
2010-03-30  9:16   ` Martin Lukasik
2010-03-30  9:23     ` Keir Fraser
2010-03-30  9:26     ` Pasi Kärkkäinen
2010-03-30  9:32       ` Martin Lukasik
2010-03-30  9:39         ` Pasi Kärkkäinen
2010-03-30  9:43         ` Keir Fraser
2010-03-29 16:00 ` Jan Beulich
2010-03-29 16:03   ` Martin Lukasik
2010-03-29 16:17     ` Jan Beulich
2010-03-29 16:27 ` Keir Fraser

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=4BB1D8C60200007800037C33@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=martin.lukasik@cancer.org.uk \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).