Date: Fri, 21 Nov 2025 18:51:58 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 290793] iovctl on mlx5en won't work Message-ID: <bug-290793-7501-XR6NtkPuU3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-290793-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-290793-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290793 --- Comment #4 from Bjoern A. Zeeb <bz@FreeBSD.org> --- (In reply to David BOYER from comment #3) What's the call graph into this? I can only find mlx5_core/mlx5_main.c::request_bar -> pci_request_regions() which ends up at the end of a loop in lkpi_pci_request_region(). You made me actually look at Linux code and there you end up in __pci_request_region() which has the same checks at the beginning it seems: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/pci.c#n3935 So the problem is likely elsewhere in the LinuxKPI emulation or in mlx5. Also the error logged: mlx5_core2: lkpi_pci_request_region: failed to alloc bar 0 type 3 rid 16 comes from after that check? So if it would fail and return we would not see this? Is that a secondary problem? If you say "On FreeBSD, the BAR size of VFs can temporarily be 0 and." Would we assume mlx5core to only call pci_request_regions() once they are properly initialized? I am trying to get access to a mlx5 in order to see if I can dig into this but someone who knows the driver should likely be able to do this a lot easier than I. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-290793-7501-XR6NtkPuU3>