From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40247) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TdUGm-0005Ec-JP for qemu-devel@nongnu.org; Tue, 27 Nov 2012 18:08:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TdUGl-0002Ln-87 for qemu-devel@nongnu.org; Tue, 27 Nov 2012 18:08:48 -0500 Received: from mout.web.de ([212.227.15.3]:61641) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TdUGk-0002LO-Ub for qemu-devel@nongnu.org; Tue, 27 Nov 2012 18:08:47 -0500 Message-ID: <50B547F3.1080907@web.de> Date: Wed, 28 Nov 2012 00:08:35 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <20121127215203.5751.6523.stgit@bling.home> In-Reply-To: <20121127215203.5751.6523.stgit@bling.home> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig783F0BE6916CE16B243F9B4D" Subject: Re: [Qemu-devel] [RFC PATCH 0/4] MSI affinity for assigned devices List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Williamson Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig783F0BE6916CE16B243F9B4D Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2012-11-27 23:00, Alex Williamson wrote: > This is post-1.3 material, so I'll just post it as an RFC for now. >=20 > MSI routing updates aren't currently handled by pci-assign or > vfio-pci (when using KVM acceleration), which means that trying to > set interrupt SMP affinity in the guest has no effect unless MSI is > completely disabled and re-enabled. This series fixes this for both > device assignment backends using similar schemes. We store the last > MSIMessage programmed to KVM and do updates to the MSI route when it > changes. pci-assign takes a little bit of refactoring to make this > happen cleanly. Thanks, This should rather be done by implementing vector notifiers for MSI as well. That way the device model no longer has to track reasons for vector changes in an open-coded fashion, just like we already do for MSI-= X. Was on my todo list for a long time, but I never reached this item. Jan --------------enig783F0BE6916CE16B243F9B4D 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 undefined - http://www.enigmail.net/ iEYEARECAAYFAlC1R/gACgkQitSsb3rl5xSZSgCgtK2jTaMaZ+NL+sB0oSRTIm/H /JYAnRB8MqkH9iPwIqW0+XrmkabGux/f =RCNc -----END PGP SIGNATURE----- --------------enig783F0BE6916CE16B243F9B4D--