From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Device assignment, shared IRQs, uio_pci_generic Date: Sat, 30 Oct 2010 17:58:30 +0200 Message-ID: <4CCC40A6.7080008@web.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA87F845AC0CF57D37E587CF2" To: "Michael S. Tsirkin" , Alex Williamson , kvm Return-path: Received: from fmmailgate03.web.de ([217.72.192.234]:49944 "EHLO fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752765Ab0J3QAV (ORCPT ); Sat, 30 Oct 2010 12:00:21 -0400 Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA87F845AC0CF57D37E587CF2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi all, trying to pass some host device to a KVM guest (for driver hacking), I ran into massive IRQ sharing issues on the host. Classic device assignment refuses to work in this case. I remembered uio_pci_generic, which I thought was once designed to resolve this conflict. But it isn't used by KVM or qemu, is it? So I crossed fingers and hacked IRQF_SHARED into assigned_device_enable_host_intx. Effect as expected: assignment work, host gets massive hick-ups (the graphic adapter is another user of this line...). Are there already VFIO patches ready for testing that work with shared IRQs as well? And/or would it make sense to integrate IRQ sharing via PCI-level IRQ masking to the KVM core until VFIO becomes standard? Jan --------------enigA87F845AC0CF57D37E587CF2 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.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkzMQKYACgkQitSsb3rl5xQItQCggvQ3LOkXXiiR+vcFE2hfka7m yLsAn2Y2+Y8WfCJvhb59XvYi17OpkoO5 =Pm00 -----END PGP SIGNATURE----- --------------enigA87F845AC0CF57D37E587CF2--