Re: [dpdk-dev] [PATCH] vfio: fix getting default container

2019-11-06 Thread David Marchand
On Mon, Nov 4, 2019 at 8:35 PM David Marchand wrote: > > On Mon, Nov 4, 2019 at 6:41 PM Anatoly Burakov > wrote: > > > > When requesting DMA mapping to default container, we are meant to > > supply the RTE_VFIO_DEFAULT_CONTAINER_FD value, however this is > > not handled correctly by get_vfio_cfg_

Re: [dpdk-dev] [PATCH] vfio: fix getting default container

2019-11-05 Thread Shahaf Shuler
Monday, November 4, 2019 9:35 PM, David Marchand: > Subject: Re: [PATCH] vfio: fix getting default container > > On Mon, Nov 4, 2019 at 6:41 PM Anatoly Burakov > wrote: > > > > When requesting DMA mapping to default container, we are meant to > > supply the RTE_VFIO_DEFAULT_CONTAINER_FD value, ho

Re: [dpdk-dev] [PATCH] vfio: fix getting default container

2019-11-04 Thread David Marchand
On Mon, Nov 4, 2019 at 6:41 PM Anatoly Burakov wrote: > > When requesting DMA mapping to default container, we are meant to > supply the RTE_VFIO_DEFAULT_CONTAINER_FD value, however this is > not handled correctly by get_vfio_cfg_by_container_fd(), because > it only looks at actual fd values and d

[dpdk-dev] [PATCH] vfio: fix getting default container

2019-11-04 Thread Anatoly Burakov
When requesting DMA mapping to default container, we are meant to supply the RTE_VFIO_DEFAULT_CONTAINER_FD value, however this is not handled correctly by get_vfio_cfg_by_container_fd(), because it only looks at actual fd values and does not check for this special case. Fix it to return default co