introduced this regression, 847d78fb95
("bus/pci: fix FD in secondary process"), only mentioned enabling access
to config space from secondary process, which still works, as it doesn't
rely on the device file.
Fixes: 847d78fb95 ("bus/pci: fix FD in secondary process")
Sign
: sta...@dpdk.org
Signed-off-by: Konrad Sztyber
---
drivers/bus/pci/linux/pci_uio.c | 27 +++
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/drivers/bus/pci/linux/pci_uio.c b/drivers/bus/pci/linux/pci_uio.c
index 4c1d3327a9..5c4ba8098c 100644
--- a/driver
On 10/7/24 19:49, Stephen Hemminger wrote:
On Wed, 28 Aug 2024 12:40:02 +0200
Konrad Sztyber wrote:
The uio_pci_generic driver clears the bus master bit when the device
file is closed. So, when the secondary process terminates after probing
a device, that device becomes unusable in the
On 10/9/24 17:12, Stephen Hemminger wrote:
That is what tap, and xdp are doing.
Thanks for the info. I'll take a look and will send a next rev doing
something similar in uio.
Konrad
gets it over UNIX domain socket via SCM_RIGHTS.
Fixes: 847d78fb9530 ("bus/pci: fix FD in secondary process")
Cc: sta...@dpdk.org
Signed-off-by: Konrad Sztyber
---
v3:
Use the rte_mp_* infrastructure to pass the uio fd from the primary
process to the secondary.
v2:
Fixed coding st
On 10/24/24 11:05, David Marchand wrote:
On Fri, Oct 11, 2024 at 1:17 PM Konrad Sztyber wrote:
The uio_pci_generic driver clears the bus master bit when the device
file is closed. So, when the secondary process terminates after probing
a device, that device becomes unusable in the primary
6 matches
Mail list logo