From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53651) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a9ESl-0007G0-I8 for qemu-devel@nongnu.org; Wed, 16 Dec 2015 10:58:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a9ESi-0000K5-5J for qemu-devel@nongnu.org; Wed, 16 Dec 2015 10:57:59 -0500 Received: from mx2.suse.de ([195.135.220.15]:36207) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a9ESh-0000K1-Vi for qemu-devel@nongnu.org; Wed, 16 Dec 2015 10:57:56 -0500 References: <1449728144-6223-1-git-send-email-bharata@linux.vnet.ibm.com> <567180EA.5040709@suse.de> <20151216164441.270a1f72@igors-macbook-pro.local> From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Message-ID: <56718A02.1090701@suse.de> Date: Wed, 16 Dec 2015 16:57:54 +0100 MIME-Version: 1.0 In-Reply-To: <20151216164441.270a1f72@igors-macbook-pro.local> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [RFC PATCH v0 0/9] Generic cpu-core device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Mammedov Cc: peter.maydell@linaro.org, ehabkost@redhat.com, agraf@suse.de, qemu-devel@nongnu.org, borntraeger@de.ibm.com, Bharata B Rao , pbonzini@redhat.com, david@gibson.dropbear.id.au Am 16.12.2015 um 16:44 schrieb Igor Mammedov: > On Wed, 16 Dec 2015 16:19:06 +0100 > Andreas F=C3=A4rber wrote: >=20 >> Am 10.12.2015 um 07:15 schrieb Bharata B Rao: >>> CPU hotplug granularity >>> ----------------------- >>> CPU hotplug will now be done in cpu-core device granularity. >> >> Nack. >> >>> Are there archs that would need thread level CPU addition ? >> >> Yes, s390. And for x86 people called for socket level. > socket level hotplug would be the last resort if we can't agree > on thread level one. As it would break existing setups where > user can hotplug 1 core, and I'd like to avoid it if it is possible. We still need to keep cpu-add for backwards compatibility, so I am discussing solely the new device_add interface. My previous x86 series went to severe hacks trying to keep cpu-add working with sockets&cores. Attendees in Seattle said that thread-level hot-plug were dangerous for Linux guests due to assumptions in the (guest's) scheduler breaking for any incompletely filled cores or sockets. No one present objected to doing it on socket level. Bharata(?) had a recent patch to catch such incompletely filled cores on the initial command line and I think we should seriously consider doing that even if it breaks some fringe use case - hot-added incomplete cores or sockets remain to be detected. Regards, Andreas --=20 SUSE Linux GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Felix Imend=C3=B6rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N= =C3=BCrnberg)