[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3cf2178e917fc345bc4cafee5af4a81f555725ec.camel@redhat.com>
Date: Tue, 02 Jul 2024 12:39:33 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Shay Drory <shayd@...dia.com>, netdev@...r.kernel.org,
davem@...emloft.net, kuba@...nel.org, edumazet@...gle.com,
gregkh@...uxfoundation.org, david.m.ertman@...el.com
Cc: rafael@...nel.org, ira.weiny@...el.com, linux-rdma@...r.kernel.org,
leon@...nel.org, tariqt@...dia.com, Simon Horman <horms@...nel.org>, Parav
Pandit <parav@...dia.com>
Subject: Re: [PATCH net-next v8 1/2] driver core: auxiliary bus: show
auxiliary device IRQs
On Thu, 2024-06-27 at 17:38 +0300, Shay Drory wrote:
> PCI subfunctions (SF) are anchored on the auxiliary bus. PCI physical
> and virtual functions are anchored on the PCI bus. The irq information
> of each such function is visible to users via sysfs directory "msi_irqs"
> containing files for each irq entry. However, for PCI SFs such
> information is unavailable. Due to this users have no visibility on IRQs
> used by the SFs.
> Secondly, an SF can be multi function device supporting rdma, netdevice
> and more. Without irq information at the bus level, the user is unable
> to view or use the affinity of the SF IRQs.
>
> Hence to match to the equivalent PCI PFs and VFs, add "irqs" directory,
> for supporting auxiliary devices, containing file for each irq entry.
>
> For example:
> $ ls /sys/bus/auxiliary/devices/mlx5_core.sf.1/irqs/
> 50 51 52 53 54 55 56 57 58
>
> Cc: Simon Horman <horms@...nel.org>
> Reviewed-by: Parav Pandit <parav@...dia.com>
> Signed-off-by: Shay Drory <shayd@...dia.com>
>
> ---
> v7-v8:
> - use cleanup.h for info and name fields (Greg)
AFAICT Greg (also) asked about using guards for the lock.
Thanks,
Paolo
Powered by blists - more mailing lists