[vfio-users] lspci and vfio_pci_release deadlock when destroy a pci passthrough VM

Hi Alex, I notice a patch you pushed in https://lkml.org/lkml/2019/2/18/1315 You said the previous commit you pushed may prone to deadlock, could you please share the details about how to reproduce the deadlock scene if you know it. I met a similar question that all lspci command went into D stat

Re: [vfio-users] PLX switch report a UR when EP tries to DMA to VM's memory

> > > > > Hi, > > > > > > > > > > I notice a problem with a PCIe endpoint, which is behind a PLX > switch, > > > > assigned to a VM by VFIO. > > > > > The problem is switch report a UR error when the EP tries to DMA > to a > > > > memory zone inside VM's address space. > > > > > Assume that the DMA

Re: [vfio-users] PLX switch report a UR when EP tries to DMA to VM's memory

> > Hi, > > > > I notice a problem with a PCIe endpoint, which is behind a PLX switch, > assigned to a VM by VFIO. > > The problem is switch report a UR error when the EP tries to DMA to a > memory zone inside VM's address space. > > Assume that the DMA destination address is between in the VM's ra

[vfio-users] PLX switch report a UR when EP tries to DMA to VM's memory

Hi, I notice a problem with a PCIe endpoint, which is behind a PLX switch, assigned to a VM by VFIO. The problem is switch report a UR error when the EP tries to DMA to a memory zone inside VM's address space. Assume that the DMA destination address is between in the VM's ram address space, and

Re: [vfio-users] host crash when assign 4 nics to 4 vms separately

> > Hi, > > > > Recently my colleague ran into a kernel crash problem when he tried to > assign 4 nics to 4 vms separately. > > Unfortunately he didn't collect related logs and we only can see the > dmesg log when core dump currently. > > > > Here the info: > > > > linux:~ # lspci | grep -i eth > >

[vfio-users] host crash when assign 4 nics to 4 vms separately

Hi, Recently my colleague ran into a kernel crash problem when he tried to assign 4 nics to 4 vms separately. Unfortunately he didn't collect related logs and we only can see the dmesg log when core dump currently. Here the info: linux:~ # lspci | grep -i eth 02:00.0 Ethernet controller: Broad

[vfio-users] How does a vfio container related to a iommu_domain

Hi, I noted that the comments in vfio_iommu_type1_attach_group: /* * Try to match an existing compatible domain. We don't want to * preclude an IOMMU driver supporting multiple bus_types and being * able to include different bus_typ

Re: [vfio-users] win7 report that the device cannot find enough free resources with a GPU behind a pci bridge

> > Hi, > > > > I found that win7/win2012r2 reported "This device cannot find enough > free resources that it can use" > > with a NVIDIA GPU passthrough behind a PCI Bridge. > > Here is a part of my xml: > > > > > > > >> function='0x0'/> > > > > > >

[vfio-users] win7 report that the device cannot find enough free resources with a GPU behind a pci bridge

Hi, I found that win7/win2012r2 reported "This device cannot find enough free resources that it can use" with a NVIDIA GPU passthrough behind a PCI Bridge. Here is a part of my xml: There is a similar problem in htt

Re: [vfio-users] qemu stuck when hot-add memory to a virtual machine with a device passthrough

> > > > Hi, > > > > > > > > The qemu process will stuck when hot-add large size memory to > > > > the virtual machine with a device passtrhough. > > > > We found it is too slow to pin and map pages in vfio_dma_do_map. > > > > Is there any method to improve this process? > > > > > > At what size d

Re: [vfio-users] qemu stuck when hot-add memory to a virtual machine with a device passthrough

> > > > Hi, > > > > > > > > The qemu process will stuck when hot-add large size memory to > > > > the virtual machine with a device passtrhough. > > > > We found it is too slow to pin and map pages in vfio_dma_do_map. > > > > Is there any method to improve this process? > > > > > > At what size d

Re: [vfio-users] qemu stuck when hot-add memory to a virtual machine with a device passthrough

> > Hi, > > > > The qemu process will stuck when hot-add large size memory to the > > virtual machine with a device passtrhough. > > We found it is too slow to pin and map pages in vfio_dma_do_map. > > Is there any method to improve this process? > > At what size do you start to see problems? T

[vfio-users] qemu stuck when hot-add memory to a virtual machine with a device passthrough

Hi, The qemu process will stuck when hot-add large size memory to the virtual machine with a device passtrhough. We found it is too slow to pin and map pages in vfio_dma_do_map. Is there any method to improve this process? Thanks, Zongyong Wu ___ vf

[vfio-users] 答复: Is there some method to merge 2 iommu group if I disable ACS

> On Mon, 7 Aug 2017 06:43:30 -0600 > Alex Williamson wrote: > > > On Aug 7, 2017 5:39 AM, "Wuzongyong (Euler Dept)" > > > > wrote: > > > > Hi, > > > > > > > > Assume that an endpoint device(called ep1) belongs to iommu gr

[vfio-users] 撤回: Is there some method to merge 2 iommu group if I disable ACS ?

Wuzongyong (Euler Dept) 将撤回邮件“Is there some method to merge 2 iommu group if I disable ACS ?”。 ___ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users

[vfio-users] Is there some method to merge 2 iommu group if I disable ACS ?

Hi, Assume that an endpoint device(called ep1) belongs to iommu group 1, and another endpoint device(called ep2) belongs to iommu group 2. Moreover, these two devices locate in different downstream ports of the same switch respectively. If I disable the ACS of these downstream ports, we know ep

[vfio-users] Is there some method to merge 2 iommu group if I disable ACS

Hi, Assume that an endpoint device(called ep1) belongs to iommu group 1, and another endpoint device(called ep2) belongs to iommu group 2. Moreover, these two devices locate in different downstream ports of the same switch respectively. If I disable the ACS of these downstream ports, we know ep