From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:39571) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S79RA-0004Ds-PW for qemu-devel@nongnu.org; Mon, 12 Mar 2012 13:53:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S79R4-00039j-Hh for qemu-devel@nongnu.org; Mon, 12 Mar 2012 13:53:36 -0400 Received: from cantor2.suse.de ([195.135.220.15]:50332 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S79R4-00039Y-8V for qemu-devel@nongnu.org; Mon, 12 Mar 2012 13:53:30 -0400 Message-ID: <4F5E3817.4010105@suse.de> Date: Mon, 12 Mar 2012 18:53:27 +0100 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= MIME-Version: 1.0 References: <20120309210403.GA2319@redhat.com> <20120310124246.GA4408@redhat.com> <20120310155843.GJ2914@otherpad.lan.raisama.net> <4F5B9C6F.3050705@codemonkey.ws> <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> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: Peter Maydell , Alexander Graf Cc: "Liu, Jinsong" , Eduardo Habkost , Gleb Natapov , libvir-list@redhat.com, Jan Kiszka , qemu-devel@nongnu.org, Avi Kivity , Anthony Liguori , Igor Mammedov , Jiri Denemark , "arch@ovirt.org" 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... 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 resets it. For ppc and sparc I don't know but I'd be surprised if it's necessary for ppc... Alex? Andreas --=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=BC= rnberg