From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH] x86: make the dom0_max_vcpus option more flexible Date: Tue, 8 May 2012 14:58:44 +0100 Message-ID: <4FA92694.4000204@citrix.com> References: <1336147301-12681-1-git-send-email-david.vrabel@citrix.com> <4FA41BF20200007800081BFE@nat28.tlf.novell.com> <4FA40321.3080201@citrix.com> <4FA41D83.2010809@citrix.com> <4FA7A1AB0200007800081F71@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FA7A1AB0200007800081F71@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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 > > Acked-by: Jan Beulich > > 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