From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48408) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YprHg-0007Y8-J4 for qemu-devel@nongnu.org; Wed, 06 May 2015 00:50:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YprHc-0003Cw-J1 for qemu-devel@nongnu.org; Wed, 06 May 2015 00:50:12 -0400 Received: from e23smtp08.au.ibm.com ([202.81.31.141]:56480) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YprHb-000394-VJ for qemu-devel@nongnu.org; Wed, 06 May 2015 00:50:08 -0400 Received: from /spool/local by e23smtp08.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 6 May 2015 14:50:04 +1000 Date: Wed, 6 May 2015 10:19:07 +0530 From: Bharata B Rao Message-ID: <20150506044907.GL18380@in.ibm.com> References: <1429858066-12088-1-git-send-email-bharata@linux.vnet.ibm.com> <1429858066-12088-11-git-send-email-bharata@linux.vnet.ibm.com> <20150505064908.GH14090@voom.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150505064908.GH14090@voom.redhat.com> Subject: Re: [Qemu-devel] [RFC PATCH v3 10/24] ppc: Update cpu_model in MachineState 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, qemu-ppc@nongnu.org, tyreld@linux.vnet.ibm.com, nfont@linux.vnet.ibm.com, imammedo@redhat.com, afaerber@suse.de On Tue, May 05, 2015 at 04:49:08PM +1000, David Gibson wrote: > On Fri, Apr 24, 2015 at 12:17:32PM +0530, Bharata B Rao wrote: > > Keep cpu_model field in MachineState uptodate so that it can be used > > from the CPU hotplug path. > > > > Signed-off-by: Bharata B Rao > > Reviewed-by: David Gibson > > As before, this looks fine to me, but I'm not sure which tree it > should go through. > > Alex, do you want to take it directly, or send an Acked-by and I'll > take it through spapr-next? In addition to this patch, there are a few other patches that are required by hotplug but can go in independently. 03/24 - spapr: Consider max_cpus during xics initialization 04/24 - spapr: Support ibm,lrdr-capacity device tree property 05/24 - spapr: Reorganize CPU dt generation code (Maybe?) 06/24 - spapr: Consolidate cpu init code into a routine 18/24 - xics_kvm: Don't enable KVM_CAP_IRQ_XICS if already enabled 19/24 - xics_kvm: Add cpu_destroy method to XICS Should I post these as a separate set (pre-requisites for sPAPR CPU hotplug) so that they can be pushed independently of the core hotplug patchset ? Regards, Bharata.