Re: [PATCH 1/2] eal/linux: fix VFIO hotplug with multiprocess

2024-10-04 Thread David Marchand
Hello Anatoly, On Mon, Sep 16, 2024 at 2:31 PM David Marchand wrote: > > At the moment, if VFIO is not available at DPDK init, it won't be > available unless a subsequent rte_vfio_enable() is done. > > Yet, even if rte_vfio_enable() is called again in primary and secondary > processes, a secondar

Re: [PATCH 1/2] eal/linux: fix VFIO hotplug with multiprocess

2024-10-03 Thread Kevin Traynor
On 02/10/2024 14:31, David Marchand wrote: > On Tue, Sep 17, 2024 at 10:20 AM Maxime Coquelin > wrote: >> On 9/16/24 14:30, David Marchand wrote: >>> At the moment, if VFIO is not available at DPDK init, it won't be >>> available unless a subsequent rte_vfio_enable() is done. >>> >>> Yet, even if

Re: [PATCH 1/2] eal/linux: fix VFIO hotplug with multiprocess

2024-10-02 Thread David Marchand
On Tue, Sep 17, 2024 at 10:20 AM Maxime Coquelin wrote: > On 9/16/24 14:30, David Marchand wrote: > > At the moment, if VFIO is not available at DPDK init, it won't be > > available unless a subsequent rte_vfio_enable() is done. > > > > Yet, even if rte_vfio_enable() is called again in primary and

Re: [PATCH 1/2] eal/linux: fix VFIO hotplug with multiprocess

2024-09-17 Thread Maxime Coquelin
On 9/16/24 14:30, David Marchand wrote: At the moment, if VFIO is not available at DPDK init, it won't be available unless a subsequent rte_vfio_enable() is done. Yet, even if rte_vfio_enable() is called again in primary and secondary processes, a secondary process will never get to know that

[PATCH 1/2] eal/linux: fix VFIO hotplug with multiprocess

2024-09-16 Thread David Marchand
At the moment, if VFIO is not available at DPDK init, it won't be available unless a subsequent rte_vfio_enable() is done. Yet, even if rte_vfio_enable() is called again in primary and secondary processes, a secondary process will never get to know that VFIO has been enabled in the primary process