From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36358) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SXtZB-00050E-AK for qemu-devel@nongnu.org; Fri, 25 May 2012 08:24:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SXtZ6-0005Qe-Mf for qemu-devel@nongnu.org; Fri, 25 May 2012 08:24:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43917) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SXtZ6-0005QM-Es for qemu-devel@nongnu.org; Fri, 25 May 2012 08:24:20 -0400 Message-ID: <1337948650.4714.88.camel@ul30vt> From: Alex Williamson Date: Fri, 25 May 2012 06:24:10 -0600 In-Reply-To: <1337934518.16119.15.camel@pasglop> References: <4FBF3627.3030504@ozlabs.ru> <1337934518.16119.15.camel@pasglop> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Subject: Re: [Qemu-devel] [RFC PATCH] vfio: add fixup for broken PCI devices List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Benjamin Herrenschmidt Cc: Alexey Kardashevskiy , qemu-devel@nongnu.org, Alex Graf , kvm@vger.kernel.org, David Gibson On Fri, 2012-05-25 at 18:28 +1000, Benjamin Herrenschmidt wrote: > On Fri, 2012-05-25 at 17:35 +1000, Alexey Kardashevskiy wrote: > > Some adapters (like NEC PCI USB controller) do not flush their config > > on a sioftware reset and remember DMA config, etc. > > > > If we use such an adapter with QEMU, then crash QEMU (stop it with > > ctrl-A ctrl-X), and try to use it in QEMU again, it may start working > > immediately with previous config when pci_enable_device() is called > > on that PCI function. > > > > To eliminate such effect, some quirk should be called. The proposed > > pci_fixup_final does its job well for mentioned NEC PCI USB but not > > sure if it is 100% correct. > > I think we should create a new quirk category... call it pci_fixup_reset > or something like that, which is responsible for blasting the thing into > submission when ownership changes. > > We'll need these for more than just USB I suspect. We already have pci_dev_specific_reset() called from pci_dev_reset(). Does this device support any of the standard reset mechanisms? It would be nice to know what within the final fixups keeps this device working. Thanks, Alex