Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-24 Thread Burakov, Anatoly
Hi Alejandro, > I have tested this approach and it works for the single device per group > case, which is the one I can test by now. But I'm not sure I understood this > comment about using a old kernel for testing the multiple devices per group > case. Can you confirm if I understood this corr

Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-18 Thread Alejandro Lucero
On Thu, Apr 6, 2017 at 11:10 AM, Burakov, Anatoly wrote: > Hi Alejandro, > > > Yes, the code was not aware of that possibility. Being honest, I knew > about that, but not in my mind when implementing the code. I have just > cards where each PF even VF have their own VFIO group. This could be a >

Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-06 Thread Burakov, Anatoly
Hi Alejandro, > Yes, the code was not aware of that possibility. Being honest, I knew about > that, but not in my mind when implementing the code. I have just cards where > each PF even VF have their own VFIO group. This could be a problem for > testing. > Anatoly, do you have a system with tha

Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-05 Thread Alejandro Lucero
On Tue, Apr 4, 2017 at 5:20 PM, Burakov, Anatoly wrote: > Hi Andrew, > > > Please, take a look at http://dpdk.org/dev/patchwork/patch/23202/ > > I took a quick look. It should fix the problem (closing the group will > cause container detachment, so we can always assume that if there's no > contai

Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-05 Thread Alejandro Lucero
Hi Andrew, Anatoly, On Tue, Apr 4, 2017 at 4:52 PM, Burakov, Anatoly wrote: > Hi Andrew, > > > I think a key to the main problem is the same IOMMU group used for both > PCI functions. > > It tries to set IOMMU type using the same file descriptor twice. The > second set is dummy, since the same v

Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-04 Thread Burakov, Anatoly
Hi Andrew, > Please, take a look at http://dpdk.org/dev/patchwork/patch/23202/ I took a quick look. It should fix the problem (closing the group will cause container detachment, so we can always assume that if there's no container associated with the group, there are no devices within that grou

Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-04 Thread Andrew Rybchenko
On 04/04/2017 06:52 PM, Burakov, Anatoly wrote: Hi Andrew, I think a key to the main problem is the same IOMMU group used for both PCI functions. It tries to set IOMMU type using the same file descriptor twice. The second set is dummy, since the same value is set, but still fails, I guess, be

Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-04 Thread Burakov, Anatoly
Hi Andrew, > I think a key to the main problem is the same IOMMU group used for both PCI > functions. > It tries to set IOMMU type using the same file descriptor twice. The second > set is dummy, since the same value is set, but still fails, I guess, because > it is already in use. > See logs w

Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-04 Thread Andrew Rybchenko
On 04/03/2017 07:11 PM, Burakov, Anatoly wrote: From: Andrew Rybchenko [mailto:arybche...@solarflare.com] Sent: Saturday, April 1, 2017 11:47 AM To: dev@dpdk.org; Alejandro Lucero Cc: Burakov, Anatoly Subject: vfio: failed to select IOMMU type Hi, after the following commit (it was picked up

Re: [dpdk-dev] vfio: failed to select IOMMU type

2017-04-03 Thread Burakov, Anatoly
> From: Andrew Rybchenko [mailto:arybche...@solarflare.com] > Sent: Saturday, April 1, 2017 11:47 AM > To: dev@dpdk.org; Alejandro Lucero > Cc: Burakov, Anatoly > Subject: vfio: failed to select IOMMU type > > Hi, > > after the following commit (it was picked up by dpdk-next-net recently), I >