From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40069) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S79T6-00053b-7Z for qemu-devel@nongnu.org; Mon, 12 Mar 2012 13:55:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S79T4-0003rT-62 for qemu-devel@nongnu.org; Mon, 12 Mar 2012 13:55:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17763) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S79T3-0003rK-Tn for qemu-devel@nongnu.org; Mon, 12 Mar 2012 13:55:34 -0400 Date: Mon, 12 Mar 2012 19:55:24 +0200 From: Gleb Natapov Message-ID: <20120312175523.GJ12353@redhat.com> References: <20120311132755.GJ17882@redhat.com> <4F5CB2EA.10000@codemonkey.ws> <20120311145655.GK17882@redhat.com> <4F5CC5BB.3070000@codemonkey.ws> <20120311161625.GN17882@redhat.com> <4F5E1B1B.1040606@suse.de> <20120312165014.GA25451@otherpad.lan.raisama.net> <4F5E3532.4060003@suse.de> <4F5E3817.4010105@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <4F5E3817.4010105@suse.de> Subject: Re: [Qemu-devel] [libvirt] Modern CPU models cannot be used with libvirt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andreas =?utf-8?Q?F=C3=A4rber?= Cc: "Liu, Jinsong" , Peter Maydell , Eduardo Habkost , libvir-list@redhat.com, Jan Kiszka , Alexander Graf , qemu-devel@nongnu.org, Avi Kivity , Anthony Liguori , Igor Mammedov , Jiri Denemark , "arch@ovirt.org" On Mon, Mar 12, 2012 at 06:53:27PM +0100, Andreas F=C3=A4rber wrote: > Am 12.03.2012 18:47, schrieb Peter Maydell: > > On 12 March 2012 17:41, Andreas F=C3=A4rber wrote: > >> Also keep in mind linux-user. There's no concept of a machine there, b= ut > >> there's a cpu_copy() function used for forking that tries to re-create > >> the CPU based on its model. > >=20 > > Incidentally, do you know why the linux-user code calls cpu_reset on > > the newly copied CPU state but only for TARGET_I386/SPARC/PPC ? That > > looks very odd to me... >=20 > Incidentally for i386 I do: cpu_reset() is intentionally not part of > cpu_init() there because afterwards the machine or something sets > whether this CPU is a "bsp" (Board Support Package? ;)) and only then Boot Strap Processor I guess :) > resets it. >=20 > For ppc and sparc I don't know but I'd be surprised if it's necessary > for ppc... Alex? >=20 > Andreas >=20 > --=20 > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3= =BCrnberg -- Gleb.