All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: make the dom0_max_vcpus option more flexible
Date: Tue, 8 May 2012 14:58:44 +0100	[thread overview]
Message-ID: <4FA92694.4000204@citrix.com> (raw)
In-Reply-To: <4FA7A1AB0200007800081F71@nat28.tlf.novell.com>

On 07/05/12 09:19, Jan Beulich wrote:
>> Subject: [PATCH] x86: make the dom0_max_vcpus option more flexible
>>
>> The dom0_max_vcpus command line option only allows the exact number of
>> VCPUs for dom0 to be set.  It is not possible to say "up to N VCPUs
>> but no more than the number physically present."
>>
>> Allow a range for the option to set a minimum number of VCPUs, and a
>> maximum which does not exceed the number of PCPUs.
>>
>> For example, with "dom0_max_vcpus=4-8":
>>
>>     PCPUs  Dom0 VCPUs
>>      2      4
>>      4      4
>>      6      6
>>      8      8
>>     10      8
>>
>> Existing command lines with "dom0_max_vcpus=N" still work as before.
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> 
> Acked-by: Jan Beulich <jbeulich@suse.com>
> 
> But I'm not sure whether this qualifies for going in for 4.2...

I don't think it's a 4.2 candidate.  I posted it now we need this
functionality in XenServer and I didn't want to change the command line
in a way that would be incompatible with upstream.

David

  reply	other threads:[~2012-05-08 13:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 16:01 [PATCH] x86: make the dom0_max_vcpus option more flexible David Vrabel
2012-05-04 16:12 ` Jan Beulich
2012-05-04 16:26   ` David Vrabel
2012-05-04 18:18     ` David Vrabel
2012-05-07  8:19       ` Jan Beulich
2012-05-08 13:58         ` David Vrabel [this message]
2012-05-07  6:42     ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2012-09-10 17:26 David Vrabel
2012-09-11  7:05 ` Jan Beulich

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=4FA92694.4000204@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    /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.