From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56006) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3xjW-00081b-Q7 for qemu-devel@nongnu.org; Tue, 01 Dec 2015 22:05:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a3xjS-0005tG-PJ for qemu-devel@nongnu.org; Tue, 01 Dec 2015 22:05:30 -0500 Received: from e23smtp02.au.ibm.com ([202.81.31.144]:49000) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3xjR-0005rz-Tb for qemu-devel@nongnu.org; Tue, 01 Dec 2015 22:05:26 -0500 Received: from localhost by e23smtp02.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 2 Dec 2015 13:05:20 +1000 Date: Wed, 2 Dec 2015 08:34:20 +0530 From: Bharata B Rao Message-ID: <20151202030420.GB16342@in.ibm.com> References: <1448024079-20808-1-git-send-email-bharata@linux.vnet.ibm.com> <1448024079-20808-2-git-send-email-bharata@linux.vnet.ibm.com> <20151201003703.GH24766@voom.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151201003703.GH24766@voom.redhat.com> Subject: Re: [Qemu-devel] [PATCH v5 01/10] vl: Don't allow CPU toplogies with partially filled cores Reply-To: bharata@linux.vnet.ibm.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Gibson Cc: mdroth@linux.vnet.ibm.com, aik@ozlabs.ru, agraf@suse.de, qemu-devel@nongnu.org, pbonzini@redhat.com, qemu-ppc@nongnu.org, tyreld@linux.vnet.ibm.com, nfont@linux.vnet.ibm.com, imammedo@redhat.com, afaerber@suse.de On Tue, Dec 01, 2015 at 11:37:03AM +1100, David Gibson wrote: > On Fri, Nov 20, 2015 at 06:24:30PM +0530, Bharata B Rao wrote: > > Prevent guests from booting with CPU topologies that have partially > > filled CPU cores or can result in partially filled CPU cores after > > CPU hotplug like > > > > -smp 15,sockets=1,cores=4,threads=4,maxcpus=16 or > > -smp 15,sockets=1,cores=4,threads=4,maxcpus=17. > > > > Signed-off-by: Bharata B Rao > > Reviewed-by: David Gibson > > I may have missed a bit of the discussion leading up to this. What > was the rationale for still allowing partially filled sockets (and > otherwise doing things at core rather than socket level?) This is generic parsing code. I don't remember an explicit discussion around allowing or dis-allowing paritialy filled sockets. I thought disallowing partially filled cores from generic smp parsing code would be an acceptable first step for all archs. Regards, Bharata.