From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34339) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWi5t-0000MC-93 for qemu-devel@nongnu.org; Fri, 19 Feb 2016 05:15:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aWi5o-00033Q-8p for qemu-devel@nongnu.org; Fri, 19 Feb 2016 05:15:25 -0500 Received: from mout.web.de ([212.227.15.4]:58945) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aWi5n-00033C-V5 for qemu-devel@nongnu.org; Fri, 19 Feb 2016 05:15:20 -0500 References: <1455852618-5224-1-git-send-email-peterx@redhat.com> <56C6BA42.1050302@web.de> <20160219074300.GC17229@pxdev.xzpeter.org> <56C6D3A0.9070302@web.de> <20160219092931.GD17229@pxdev.xzpeter.org> <56C6E734.90204@redhat.com> From: Jan Kiszka Message-ID: <56C6EB2A.1010503@web.de> Date: Fri, 19 Feb 2016 11:15:06 +0100 MIME-Version: 1.0 In-Reply-To: <56C6E734.90204@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8BAWhlHCVjwJTlGb7khNfXXECA5hk2t6H" Subject: Re: [Qemu-devel] [PATCH 00/13] IOMMU: Enable interrupt remapping for Intel IOMMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , Peter Xu , Rita Sinha Cc: ehabkost@redhat.com, =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , jasowang@redhat.com, mst@redhat.com, qemu-devel@nongnu.org, imammedo@redhat.com, rth@twiddle.net This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8BAWhlHCVjwJTlGb7khNfXXECA5hk2t6H Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-02-19 10:58, Paolo Bonzini wrote: >=20 >=20 > On 19/02/2016 10:29, Peter Xu wrote: >> On Fri, Feb 19, 2016 at 09:34:40AM +0100, Jan Kiszka wrote: >>> On 2016-02-19 08:43, Peter Xu wrote: >>>> Actually there are several people within my working team knows that >>>> I would be working on this, and I believe none of us do know your >>>> work too... Or there must be someone telling me so... >>> >>> I guess we would have to match sets of people know to find out who >>> forgot to mention the outreachy project ;) - anyway, this can always = happen. >=20 > I knew about the outreachy project and forgot to mention it... but then= , > I only learnt about your effort yesterday. :) >=20 >>> I didn't look into your approach in all details yet, and Rita also ju= st >>> started, she told me. So one question on yours - which looks appealin= g >>> from the invasiveness POV - is how you determine the MSI source with >>> only a single target region? I do find your changes on the IOAPIC, bu= t >>> none on the PCI infrastructure, which is confusing given that you say= >>> that works, no? >> >> Do we need to know the source of the MSI interrupt to >> translate/deliver it? Maybe I got something missing, but could you >> explain why we need it? >=20 > I think you're not verifying the SVT, SID and SQ fields in the IRTE. Exactly. >=20 > The source ID can be passed to the IOMMU using the MemTxAttrs mechanism= =2E Ah, that's a nice new channel, resolving the need for using/passing source-specific target memory regions for this. At least for PCI devices, it should already be populated with the required information, others (IOAPIC, HPET) probably require additional work to pass what I defined as Q35_PSEUDO_BUS_PLATFORM, Q35_PSEUDO_DEVFN_IOAPIC/HPET. Jan --8BAWhlHCVjwJTlGb7khNfXXECA5hk2t6H 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 iEYEARECAAYFAlbG6yoACgkQitSsb3rl5xTo9gCfbp6g14i25a/1tCuAAWQltkS2 ihMAn3XSJOW+D9NUPubA/JTozk4BDBcS =5fR1 -----END PGP SIGNATURE----- --8BAWhlHCVjwJTlGb7khNfXXECA5hk2t6H--