From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55738) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SCn4Y-00049W-2p for qemu-devel@nongnu.org; Wed, 28 Mar 2012 03:13:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SCn4T-0005KE-9n for qemu-devel@nongnu.org; Wed, 28 Mar 2012 03:13:33 -0400 Received: from fmmailgate07.web.de ([217.72.192.248]:42398) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SCn4T-0005K8-0B for qemu-devel@nongnu.org; Wed, 28 Mar 2012 03:13:29 -0400 Received: from moweb002.kundenserver.de (moweb002.kundenserver.de [172.19.20.108]) by fmmailgate07.web.de (Postfix) with ESMTP id 2C776FB4383 for ; Wed, 28 Mar 2012 09:13:27 +0200 (CEST) Message-ID: <4F72BA12.2080309@web.de> Date: Wed, 28 Mar 2012 09:13:22 +0200 From: Jan Kiszka MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2DE44B3ABE90543F9CA0DE46" Subject: Re: [Qemu-devel] [RFC][PATCH 0/2] uq/master: Basic MSI support for in-kernel irqchip mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity , Marcelo Tosatti Cc: qemu-devel , kvm@vger.kernel.org, "Michael S. Tsirkin" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2DE44B3ABE90543F9CA0DE46 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 2012-03-22 00:17, Jan Kiszka wrote: > Some half a year ago when I posted my first attempt to refactor MSI > for KVM support, we came to the conclusion that it might suffice to do > transparent dynamic routing for user-space injected MSI messages. These= > two patches now implement such an approach for upstream. >=20 > As QEMU does not yet include irqfd support (for vhost) or pci device > assignment, this is already enough to enable MSI over the in-kernel > irqchip. Still, this is only RFC as it is just lightly tested and shoul= d > primarily collect feedback regarding the direction. If it's fine, I'd > like to base further qemu-kvm refactorings and upstream preparations on= > top of such a series. >=20 > Also, I'd like to reanimate my KVM patch to provide direct MSI injectio= n > in future kernels so that we do not need to take this long path here > forever. >=20 > Jan Kiszka (2): > kvm: Introduce basic MSI support in-kernel irqchips > KVM: x86: Wire up MSI support for in-kernel irqchip >=20 > hw/apic.c | 3 + > hw/kvm/apic.c | 33 ++++++++++- > hw/pc.c | 5 -- > kvm-all.c | 171 +++++++++++++++++++++++++++++++++++++++++++++++++= +++++++- > kvm.h | 1 + > 5 files changed, 205 insertions(+), 8 deletions(-) >=20 Anyone any comments? I think this series could open the door for kernel_irqchip=3Don as default in QEMU 1.1. Jan --------------enig2DE44B3ABE90543F9CA0DE46 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/ iEYEARECAAYFAk9yuhUACgkQitSsb3rl5xQDcQCeJPDm7ZytJp4RzQ0I7Dqyzu7T t7YAoJaUOqoOBo5A8t2Mvidk6Tz7DMpz =cXd6 -----END PGP SIGNATURE----- --------------enig2DE44B3ABE90543F9CA0DE46--