From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52121) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c9mbO-00035y-VP for qemu-devel@nongnu.org; Thu, 24 Nov 2016 00:29:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c9mbL-0003VA-0d for qemu-devel@nongnu.org; Thu, 24 Nov 2016 00:29:42 -0500 Date: Thu, 24 Nov 2016 13:29:31 +0800 From: Peter Xu Message-ID: <20161124052931.GA15021@pxdev.xzpeter.org> References: <1479802130-22640-1-git-send-email-peterx@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1479802130-22640-1-git-send-email-peterx@redhat.com> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v2] pci: relax pci_msi_get_message() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: mst@redhat.com, david@gibson.dropbear.id.au, QEMU Stable On Tue, Nov 22, 2016 at 04:08:50PM +0800, Peter Xu wrote: > We are very strict in the past getting MSIs from commit > d1f6af6a1 ("kvm-irqchip: simplify kvm_irqchip_add_msi_route"), assuming > that MSI should be configured before hand when fetching. When we have > unrecognized configurations, we panic the system. However looks like > this is too strict to be working on some platform, and issues occured. > Firstly it's found on a ppc case and fixed by David in: >=20 > 6d17a01 vfio/pci: Fix regression in MSI routing configuration >=20 > However we encountered another case now with windows virtio driver and > reported (and possibly more): >=20 > http://bugs.debian.org/844361 >=20 > To make every driver/hardware happy, let's loosen the rule and go back > to the original behavior - instead of panic the system, when we try to > fetch MSI without configured MSI/MSI-X system, we just provide an empty > message to make drivers happy. >=20 > Reported-by: Maciej Kotli=C5=84ski > Signed-off-by: Peter Xu Sorry I should mark this as "for-2.8". Also cc stable since this bug exists since 2.7.0. Michael, do you think it can be a material for 2.8 rc2? Thanks, -- peterx