From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38841) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPZZZ-0005nt-WB for qemu-devel@nongnu.org; Tue, 19 Jul 2016 14:16:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bPZZV-00074w-1A for qemu-devel@nongnu.org; Tue, 19 Jul 2016 14:16:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:53052) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPZZU-00074s-Ou for qemu-devel@nongnu.org; Tue, 19 Jul 2016 14:16:44 -0400 References: <66583216254AFC43ADCD7BD88016E00698544F11@XSJ-PSEXMBX02.xlnx.xilinx.com> <20160719112229.409eee63@t450s.home> <20160719115522.71d80873@t450s.home> From: Marcel Apfelbaum Message-ID: <578E6E88.5040903@redhat.com> Date: Tue, 19 Jul 2016 21:16:40 +0300 MIME-Version: 1.0 In-Reply-To: <20160719115522.71d80873@t450s.home> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] VFIO PCIe Extended Capabilities List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Williamson , Spenser Gilliland Cc: "chen.fan.fnst@cn.fujitsu.com" , "qemu-devel@nongnu.org" , "Michael S. Tsirkin" On 07/19/2016 08:55 PM, Alex Williamson wrote: > On Tue, 19 Jul 2016 11:22:29 -0600 > Alex Williamson wrote: > >> On Tue, 19 Jul 2016 17:12:45 +0000 >> Spenser Gilliland wrote: >> >>> Hi, >>> >>> I noticed your patches "vfio: add pcie extended capability support" and "vfio/pci: Hide SR-IOV capability" have gone into qemu mainline. These look really good, and thanks so much for doing these. >>> >>> I was wondering if there were any side effects to removing the pci_bus_is_express check on line 1776 of hw/vfio/pci.c . >>> >>> /* Only add extended caps if we have them and the guest can see them */ >>> - if (!pci_is_express(pdev) || !pci_bus_is_express(pdev->bus) || >>> + if (!pci_is_express(pdev) || >>> !pci_get_long(pdev->config + PCI_CONFIG_SPACE_SIZE)) { >>> return 0; >>> } >>> >>> I'm asking because it looks like the defaults for libvirt/OpenStack are to create a "hostdev" stanza in the libvirt xml to define this pass through condition. However, it also appears that the "hostdev" stanza only supports pci-bridge bus connections. Thus, it's not easily possible to use this patch in a libvirt/OpenStack environment as the bus is technically a non-express bus. It looks like adding PCIe bus support to libvirt/OpenStack may be a lot more effort than a simple workaround here. >>> >>> I have tested this on my local system and it does work as intended for my use case. The following is from an OpenStack VM and shows that the 0x340 extended configuration space is passed through correctly. I've also done testing which uses this space and the results are positive. >> >> If the bus is not express then extended capabilities on the device >> should not be accessible, this would be a QEMU bug for allowing it. >> Cc'ing Marcel for that. Thanks, Hi Spencer, Indeed, if a device is attached to a PCI bus it makes no sense to advertise the extended configuration space. Can you please share the QEMU command line? Maybe is possible to make the device's bus PCIe in QEMU? > > In fact, I've tried to fix this multiple times: > > https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05384.html > https://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg02422.html > https://lists.nongnu.org/archive/html/qemu-devel/2016-01/msg03259.html > > Yet the patch remains unapplied :( I thought is it in already. Maybe Michael can add it as part of the hard freeze. And if the patch will be applied, the tweak above wouldn't help, right Alex? Thanks, Marcel >