From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58092) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXCTY-0002iC-Tu for qemu-devel@nongnu.org; Sun, 04 Dec 2011 08:51:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RXCTX-0002nB-VL for qemu-devel@nongnu.org; Sun, 04 Dec 2011 08:51:28 -0500 Received: from fmmailgate03.web.de ([217.72.192.234]:39461) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXCTX-0002n3-Jj for qemu-devel@nongnu.org; Sun, 04 Dec 2011 08:51:27 -0500 Received: from moweb002.kundenserver.de (moweb002.kundenserver.de [172.19.20.108]) by fmmailgate03.web.de (Postfix) with ESMTP id A16BC1AB34930 for ; Sun, 4 Dec 2011 14:51:26 +0100 (CET) Message-ID: <4EDB7ADC.50906@web.de> Date: Sun, 04 Dec 2011 14:51:24 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4EDB762C.7090909@redhat.com> <4EDB78DE.6000109@web.de> <4EDB7A74.4060804@redhat.com> In-Reply-To: <4EDB7A74.4060804@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDD70987995387F20150792CE" Subject: Re: [Qemu-devel] [RFC][PATCH 14/16] kvm: x86: Add user space part for in-kernel i8259 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Anthony Liguori , kvm@vger.kernel.org, "Michael S. Tsirkin" , Marcelo Tosatti , qemu-devel , Blue Swirl This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDD70987995387F20150792CE Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-12-04 14:49, Avi Kivity wrote: > On 12/04/2011 03:42 PM, Jan Kiszka wrote: >> On 2011-12-04 14:31, Avi Kivity wrote: >>> On 12/03/2011 01:17 PM, Jan Kiszka wrote: >>>> From: Jan Kiszka >>>> >>>> Introduce the alternative 'kvm-i8259' device model that exploits KVM= >>>> in-kernel acceleration. >>>> >>>> The PIIX3 initialization code is furthermore extended by KVM specifi= c >>>> IRQ route setup. Moreover, GSI injection differs in KVM mode from th= e >>>> user space model. As we can dispatch ISA-range IRQs to both IOAPIC a= nd >>>> PIC inside the kernel, we do not need to inject them separately. Thi= s is >>>> reflected by a KVM-specific GSI handler. >>>> >>>> + >>>> +qemu_irq *kvm_i8259_init(void) >>>> +{ >>>> + ISADevice *dev; >>>> + >>>> + dev =3D isa_create("kvm-i8259"); >>>> >>> >>> Same issue. Is this a different device, or an different implementati= on >>> of the same device? >> >> They are theoretically the same from guest perspective (therefore you >> can migrate between machines that differ in this). >=20 > But the name becomes part of the save/restore ABI, so you can't. Nope, the vmstate names are identical. That would ruin migration otherwise. It's just the output of info qtree & co. that changes. Jan --------------enigDD70987995387F20150792CE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7betwACgkQitSsb3rl5xQ/AACg0+taWaGIfrHUmWRRfTFZ3Tox /noAniUIN8Sh6CFNdteTDCiat1MmLTUZ =igg2 -----END PGP SIGNATURE----- --------------enigDD70987995387F20150792CE--