Introduce auxiliary bus IRQs sysfs
Subsystems (6)
v6 cover Introduce auxiliary bus IRQs sysfs
Today, PCI PFs and VFs, which are anchored on the PCI bus, display their IRQ information in the <pci_device>/msi_irqs/<irq_num> sysfs files. PCI subfunctions (SFs) are similar to PFs and VFs and these SFs are anchored on the auxiliary bus. However, these PCI SFs lack such IRQ information on the auxiliary bus, leaving users without visibility into which IRQs are used by the SFs. This absence makes it impossible to debug situations and to understand the source of interrupts/SFs for performance tuning and debug.
Additionally, the SFs are multifunctional devices supporting RDMA, network devices, clocks, and more, similar to their peer PCI PFs and VFs. Therefore, it is desirable to have SFs' IRQ information available at the bus/device level.
To overcome the above limitations, this short series extends the auxiliary bus to display IRQ information in sysfs, similar to that of PFs and VFs.
It adds an 'irqs' directory under the auxiliary device and includes an <irq_num> sysfs file within it.
For example:
$ ls /sys/bus/auxiliary/devices/mlx5_core.sf.1/irqs/ 50 51 52 53 54 55 56 57 58
Patch summary:
==============
patch-1 adds auxiliary bus to support irqs used by auxiliary device patch-2 mlx5 driver using exposing irqs for PCI SF devices via auxiliary
bus
---v5->v6:
- remove concept of shared and exclusive and hence global xarray in patch #1 (Greg).
- fix error flow in patch #2 (Przemek and Parav).v4->v5:
- addressed comments from Greg in patch #1.
v3->4:
- addressed comments from Przemek in patch #1.v2->v3:
- addressed comments from Parav and Przemek in patch #1.
- fixed a bug in patch #2.v1->v2:
- addressed comments from Greg, Simon H and kernel test boot in patch #1.
Shay Drory (2):
driver core: auxiliary bus: show auxiliary device IRQs net/mlx5: Expose SFs IRQs
Documentation/ABI/testing/sysfs-bus-auxiliary | 7 ++ drivers/base/auxiliary.c | 96 ++++++++++++++++++- drivers/net/ethernet/mellanox/mlx5/core/eq.c | 6 +- .../mellanox/mlx5/core/irq_affinity.c | 18 +++- .../ethernet/mellanox/mlx5/core/mlx5_core.h | 6 ++ .../ethernet/mellanox/mlx5/core/mlx5_irq.h | 12 ++- .../net/ethernet/mellanox/mlx5/core/pci_irq.c | 12 ++- .../ethernet/mellanox/mlx5/core/sf/dev/dev.c | 16 ++-- include/linux/auxiliary_bus.h | 24 ++++- 9 files changed, 174 insertions(+), 23 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-bus-auxiliary
Signature · 1 line
2.38.1
PATCH v6 1/2 driver core: auxiliary bus: show auxiliary device IRQs
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
---
v5-v6:
- removed concept of shared and exclusive and hence global xarray (Greg) v4-v5:
- restore global mutex and replace refcount_t with simple integer (Greg) v3->4:
- remove global mutex (Przemek)v2->v3:
- fix function declaration in case SYSFS isn't defined v1->v2:
- move #ifdefs from drivers/base/auxiliary.c to include/linux/auxiliary_bus.h (Greg)
- use EXPORT_SYMBOL_GPL instead of EXPORT_SYMBOL (Greg)
- Fix kzalloc(ref) to kzalloc(*ref) (Simon)
- Add return description in auxiliary_device_sysfs_irq_add() kdoc (Simon)
- Fix auxiliary_irq_mode_show doc (kernel test boot)
--- Documentation/ABI/testing/sysfs-bus-auxiliary | 7 ++ drivers/base/auxiliary.c | 96 ++++++++++++++++++- include/linux/auxiliary_bus.h | 24 ++++- 3 files changed, 124 insertions(+), 3 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-bus-auxiliary
Documentation/ABI/testing/sysfs-bus-auxiliary new file +7 -0
@@ -0,0 +1,7 @@ +What: /sys/bus/auxiliary/devices/.../irqs/ +Date: April, 2024 +Contact: Shay Drory <[email protected]> +Description: + The /sys/devices/.../irqs directory contains a variable set of + files, with each file is named as irq number similar to PCI PF + or VF's irq number located in msi_irqs directory.
drivers/base/auxiliary.c +95 -1
120 lines not on this page · raw message
include/linux/auxiliary_bus.h +22 -2
@@ -58,6 +58,7 @@* in * @name: Match name found by the auxiliary device driver, * @id: unique identitier if multiple devices of the same name are exported, +* @irqs: irqs xarray contains irq indices which are used by the device, * * An auxiliary_device represents a part of its parent device's functionality. * It is given a name that, combined with the registering drivers
@@ -138,6 +139,7 @@struct auxiliary_device {struct device dev;const char *name; +struct xarray irqs;u32 id; };
@@ -209,8 +211,26 @@ static inline struct auxiliary_driver *to_auxiliary_drv(struct device_driver *dr }int auxiliary_device_init (struct auxiliary_device *auxdev); -int __auxiliary_device_add (struct auxiliary_device *auxdev,const char *modname); -#define auxiliary_device_add (auxdev) __auxiliary_device_add(auxdev, KBUILD_MODNAME) +int __auxiliary_device_add (struct auxiliary_device *auxdev,const char *modname, +bool irqs_sysfs_enable); +#define auxiliary_device_add (auxdev) __auxiliary_device_add(auxdev, KBUILD_MODNAME, false) +#define auxiliary_device_add_with_irqs (auxdev) \ + __auxiliary_device_add(auxdev, KBUILD_MODNAME, true) + +#ifdef CONFIG_SYSFS +int auxiliary_device_sysfs_irq_add (struct auxiliary_device *auxdev,int irq); +void auxiliary_device_sysfs_irq_remove (struct auxiliary_device *auxdev, +int irq); +#else /* CONFIG_SYSFS */ +static inline int +auxiliary_device_sysfs_irq_add (struct auxiliary_device *auxdev,int irq) +{ +return 0 ; +} + +static inline void +auxiliary_device_sysfs_irq_remove (struct auxiliary_device *auxdev,int irq) {} +#endif static inline void auxiliary_device_uninit (struct auxiliary_device *auxdev) {
Signature · 1 line
2.38.1
Greg KH
maintainerRe: [PATCH net-next v6 1/2] driver core: auxiliary bus: show auxiliary device IRQs
Quoted 61 lines · Shay Drory
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 58Reviewed-by Parav Pandit <[email protected]>Signed-off-by Shay Drory <[email protected]>---
v5-v6:
- removed concept of shared and exclusive and hence global xarray (Greg) v4-v5:
- restore global mutex and replacerefcount_twith simple integer (Greg) v3->4:
- remove global mutex (Przemek)v2->v3:
- fix function declaration in case SYSFS isn't definedv1->v2:
- move #ifdefs fromdrivers/base/auxiliary.ctoinclude/linux/auxiliary_bus.h(Greg)
- useEXPORT_SYMBOL_GPLinstead ofEXPORT_SYMBOL(Greg)
- Fix kzalloc(ref) tokzalloc(*ref)(Simon)
- Add return description inauxiliary_device_sysfs_irq_add()kdoc (Simon)
- Fixauxiliary_irq_mode_showdoc (kernel test boot)--- Documentation/ABI/testing/sysfs-bus-auxiliary | 7 ++ drivers/base/auxiliary.c | 96 ++++++++++++++++++- include/linux/auxiliary_bus.h | 24 ++++- 3 files changed, 124 insertions(+), 3 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-bus-auxiliaryDocumentation/ABI/testing/sysfs-bus-auxiliary new file +7
-0@@ -0,0 +1,7 @@ +What: /sys/bus/auxiliary/devices/.../irqs/ +Date: April, 2024 +Contact: Shay Drory <[email protected]> +Description: + The /sys/devices/.../irqs directory contains a variable set of + files, with each file is named as irq number similar to PCI PF + or VF's irq number located in msi_irqs directory.drivers/base/auxiliary.c +0
-0
drivers/base/auxiliary.c line 161
Quoted 4 lines
drivers/base/auxiliary.c +1
-0@@ -158,6 +158,94 @@* }; */ +#ifdef CONFIG_SYSFS
People really build boxes without sysfs? Ok :(
But if so, why not move this to a whole new file? That would make it simpler to maintain.
Quoted 41 lines
drivers/base/auxiliary.c +41
-0+struct auxiliary_irq_info { +struct device_attribute sysfs_attr; +}; + +static struct attribute *auxiliary_irq_attrs[] = { +NULL +}; + +static const struct attribute_group auxiliary_irqs_group = { + .name ="irqs" , + .attrs = auxiliary_irq_attrs, +}; + +static const struct attribute_group *auxiliary_irqs_groups[] = { + &auxiliary_irqs_group, +NULL +}; + +/** +* auxiliary_device_sysfs_irq_add - add a sysfs entry for the given IRQ +* @auxdev: auxiliary bus device to add the sysfs entry. +* @irq: The associated interrupt number. +* +* This function should be called after auxiliary device have successfully +* received the irq. +* +* Return: zero on success or an error code on failure. +*/ +int auxiliary_device_sysfs_irq_add (struct auxiliary_device *auxdev,int irq) +{ +struct device *dev = &auxdev->dev; +struct auxiliary_irq_info *info; +int ret; + + info =kzalloc (sizeof (*info),GFP_KERNEL ); +if (!info) +return -ENOMEM ; + +sysfs_attr_init (&info->sysfs_attr.attr); + info->sysfs_attr.attr.name =kasprintf (GFP_KERNEL ,"%d" , irq); +if (!info->sysfs_attr.attr.name) {
drivers/base/auxiliary.c line 212
Quoted 10 lines
drivers/base/auxiliary.c +10
-0+ ret = -ENOMEM ; + goto name_err; + } + + ret =xa_insert (&auxdev->irqs, irq, info,GFP_KERNEL ); +if (ret) + goto auxdev_xa_err; + + ret =sysfs_add_file_to_group (&dev->kobj, &info->sysfs_attr.attr, + auxiliary_irqs_group.name);
Dynamic attributes are rough, because:
Quoted 24 lines
drivers/base/auxiliary.c +24
-0+if (ret) + goto sysfs_add_err; + +return 0 ; + +sysfs_add_err: +xa_erase (&auxdev->irqs, irq); +auxdev_xa_err: +kfree (info->sysfs_attr.attr.name); +name_err: +kfree (info); +return ret; +} +EXPORT_SYMBOL_GPL (auxiliary_device_sysfs_irq_add); + +/** +* auxiliary_device_sysfs_irq_remove - remove a sysfs entry for the given IRQ +* @auxdev: auxiliary bus device to add the sysfs entry. +* @irq: the IRQ to remove. +* +* This function should be called to remove an IRQ sysfs entry. +*/ +void auxiliary_device_sysfs_irq_remove (struct auxiliary_device *auxdev,int irq) +{
drivers/base/auxiliary.c line 246
Quoted 10 lines
drivers/base/auxiliary.c +10
-0+struct auxiliary_irq_info *info =xa_load (&auxdev->irqs, irq); +struct device *dev = &auxdev->dev; + +sysfs_remove_file_from_group (&dev->kobj, &info->sysfs_attr.attr, + auxiliary_irqs_group.name); +xa_erase (&auxdev->irqs, irq); +kfree (info->sysfs_attr.attr.name); +kfree (info); +} +EXPORT_SYMBOL_GPL (auxiliary_device_sysfs_irq_remove);
What is forcing you to remove the irqs after a device is removed from the system?
Why not just remove them all automatically? Why would you ever want to remove them after they were added, will they ever actually change over the lifespan of a device?
drivers/base/auxiliary.c
Quoted 8 lines
drivers/base/auxiliary.c +5
-2int auxiliary_device_init (struct auxiliary_device *auxdev); -int __auxiliary_device_add (struct auxiliary_device *auxdev,const char *modname); -#define auxiliary_device_add (auxdev) __auxiliary_device_add(auxdev, KBUILD_MODNAME) +int __auxiliary_device_add (struct auxiliary_device *auxdev,const char *modname, +bool irqs_sysfs_enable); +#define auxiliary_device_add (auxdev) __auxiliary_device_add(auxdev, KBUILD_MODNAME, false) +#define auxiliary_device_add_with_irqs (auxdev) \ + __auxiliary_device_add(auxdev, KBUILD_MODNAME, true)
Ick, no, that way lies madness.
Just keep the original function:
auxiliary_device_add()
as is.
Then, if someone DOES call auxiliary_device_sysfs_irq_add() then add the irq directory and file as needed then.
That way no "norml" paths are messed up and over time, we don't keep having an explosion of combinations of function calls to create an aux device (as we all know, this is NOT going to be the last feature ever added to them...)
thanks,
greg k-h
Re: [PATCH net-next v6 1/2] driver core: auxiliary bus: show auxiliary device IRQs
Quoted 68 lines · Greg KH
External email: Use caution opening links or attachments
Quoted 64 lines · Shay Drory
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 58Reviewed-by Parav Pandit <[email protected]>Signed-off-by Shay Drory <[email protected]>---
v5-v6:
- removed concept of shared and exclusive and hence global xarray (Greg) v4-v5:
- restore global mutex and replacerefcount_twith simple integer (Greg) v3->4:
- remove global mutex (Przemek)v2->v3:
- fix function declaration in case SYSFS isn't definedv1->v2:
- move #ifdefs fromdrivers/base/auxiliary.ctoinclude/linux/auxiliary_bus.h(Greg)
- useEXPORT_SYMBOL_GPLinstead ofEXPORT_SYMBOL(Greg)
- Fix kzalloc(ref) tokzalloc(*ref)(Simon)
- Add return description inauxiliary_device_sysfs_irq_add()kdoc (Simon)
- Fixauxiliary_irq_mode_showdoc (kernel test boot)--- Documentation/ABI/testing/sysfs-bus-auxiliary | 7 ++ drivers/base/auxiliary.c | 96 ++++++++++++++++++- include/linux/auxiliary_bus.h | 24 ++++- 3 files changed, 124 insertions(+), 3 deletions(-)create mode 100644
Documentation/ABI/testing/sysfs-bus-auxiliaryDocumentation/ABI/testing/sysfs-bus-auxiliary new file +7
-0@@ -0,0 +1,7 @@ +What: /sys/bus/auxiliary/devices/.../irqs/ +Date: April, 2024 +Contact: Shay Drory <[email protected]> +Description: + The /sys/devices/.../irqs directory contains a variable set of + files, with each file is named as irq number similar to PCI PF + or VF's irq number located in msi_irqs directory.drivers/base/auxiliary.c +0
-0@@ -158,6 +158,94 @@* }; */
Quoted 6 lines
drivers/base/auxiliary.c line 161
Quoted 1 line
drivers/base/auxiliary.c +1
-0+#ifdef CONFIG_SYSFS People really build boxes without sysfs? Ok :(
But if so, why not move this to a whole new file? That would make it simpler to maintain.
sounds good. Will move them to new sysfs.c
Quoted 46 lines
Quoted 46 lines
drivers/base/auxiliary.c +45
-0+struct auxiliary_irq_info { +struct device_attribute sysfs_attr; +}; + +static struct attribute *auxiliary_irq_attrs[] = { +NULL +}; + +static const struct attribute_group auxiliary_irqs_group = { + .name ="irqs" , + .attrs = auxiliary_irq_attrs, +}; + +static const struct attribute_group *auxiliary_irqs_groups[] = { + &auxiliary_irqs_group, +NULL +}; + +/** +* auxiliary_device_sysfs_irq_add - add a sysfs entry for the given IRQ +* @auxdev: auxiliary bus device to add the sysfs entry. +* @irq: The associated interrupt number. +* +* This function should be called after auxiliary device have successfully +* received the irq. +* +* Return: zero on success or an error code on failure. +*/ +int auxiliary_device_sysfs_irq_add (struct auxiliary_device *auxdev,int irq) +{ +struct device *dev = &auxdev->dev; +struct auxiliary_irq_info *info; +int ret; + + info =kzalloc (sizeof (*info),GFP_KERNEL ); +if (!info) +return -ENOMEM ; + +sysfs_attr_init (&info->sysfs_attr.attr); + info->sysfs_attr.attr.name =kasprintf (GFP_KERNEL ,"%d" , irq); +if (!info->sysfs_attr.attr.name) { + ret = -ENOMEM ; + goto name_err; + } +
Quoted 8 lines
drivers/base/auxiliary.c line 212
Quoted 6 lines
drivers/base/auxiliary.c +6
-0+ ret =xa_insert (&auxdev->irqs, irq, info,GFP_KERNEL ); +if (ret) + goto auxdev_xa_err; + + ret =sysfs_add_file_to_group (&dev->kobj, &info->sysfs_attr.attr, + auxiliary_irqs_group.name);Dynamic attributes are rough, because:
Your response after "because" is missing.
Can you please elaborate?
Quoted 31 lines
Quoted 31 lines
drivers/base/auxiliary.c +29
-0+if (ret) + goto sysfs_add_err; + +return 0 ; + +sysfs_add_err: +xa_erase (&auxdev->irqs, irq); +auxdev_xa_err: +kfree (info->sysfs_attr.attr.name); +name_err: +kfree (info); +return ret; +} +EXPORT_SYMBOL_GPL (auxiliary_device_sysfs_irq_add); + +/** +* auxiliary_device_sysfs_irq_remove - remove a sysfs entry for the given IRQ +* @auxdev: auxiliary bus device to add the sysfs entry. +* @irq: the IRQ to remove. +* +* This function should be called to remove an IRQ sysfs entry. +*/ +void auxiliary_device_sysfs_irq_remove (struct auxiliary_device *auxdev,int irq) +{ +struct auxiliary_irq_info *info =xa_load (&auxdev->irqs, irq); +struct device *dev = &auxdev->dev; + +sysfs_remove_file_from_group (&dev->kobj, &info->sysfs_attr.attr, + auxiliary_irqs_group.name);
Quoted 8 lines
drivers/base/auxiliary.c line 246
Quoted 5 lines
drivers/base/auxiliary.c +5
-0+xa_erase (&auxdev->irqs, irq); +kfree (info->sysfs_attr.attr.name); +kfree (info); +} +EXPORT_SYMBOL_GPL (auxiliary_device_sysfs_irq_remove);What is forcing you to remove the irqs after a device is removed from the system?
We are removing the irqs _before_ removing the device. Irqs removal is following the exact mirror of add flow.
Quoted 4 lines
Why not just remove them all automatically? Why would you ever want to remove them after they were added, will they ever actually change over the lifespan of a device?
IRQs of the SFs are allocated and removed when the resources are created.
for example, devlink reload flow that re-initialize the whole device by releasing and re-allocating new set of IRQs.
Certain driver internal health recovery flow can also trigger similar re-initialize.
Quoted 16 lines
drivers/base/auxiliary.c
Quoted 9 lines
drivers/base/auxiliary.c +5
-2int auxiliary_device_init (struct auxiliary_device *auxdev); -int __auxiliary_device_add (struct auxiliary_device *auxdev,const char *modname); -#define auxiliary_device_add (auxdev) __auxiliary_device_add(auxdev, KBUILD_MODNAME) +int __auxiliary_device_add (struct auxiliary_device *auxdev,const char *modname, +bool irqs_sysfs_enable); +#define auxiliary_device_add (auxdev) __auxiliary_device_add(auxdev, KBUILD_MODNAME, false) +#define auxiliary_device_add_with_irqs (auxdev) \ + __auxiliary_device_add(auxdev, KBUILD_MODNAME, true)Ick, no, that way lies madness.
Just keep the original function:
auxiliary_device_add()
as is.
Quoted 7 lines
Then, if someone DOES call
auxiliary_device_sysfs_irq_add()then add the irq directory and file as needed then.That way no "norml" paths are messed up and over time, we don't keep having an explosion of combinations of function calls to create an aux device (as we all know, this is NOT going to be the last feature ever added to them...)
Thanks for the suggestion, will change in next version.
Quoted 4 lines
thanks,
greg k-h
Re: [PATCH net-next v6 1/2] driver core: auxiliary bus: show auxiliary device IRQs
Quoted 74 lines · Shay Drori
Quoted 71 lines · Greg KH
External email: Use caution opening links or attachments
Quoted 67 lines · Shay Drory
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 58Reviewed-by Parav Pandit <[email protected]>Signed-off-by Shay Drory <[email protected]>---
v5-v6:
- removed concept of shared and exclusive and hence global xarray (Greg) v4-v5:
- restore global mutex and replacerefcount_twith simple integer (Greg) v3->4:
- remove global mutex (Przemek)v2->v3:
- fix function declaration in case SYSFS isn't definedv1->v2:
- move #ifdefs fromdrivers/base/auxiliary.ctoinclude/linux/auxiliary_bus.h(Greg)
- useEXPORT_SYMBOL_GPLinstead ofEXPORT_SYMBOL(Greg)
- Fix kzalloc(ref) tokzalloc(*ref)(Simon)
- Add return description inauxiliary_device_sysfs_irq_add()kdoc (Simon)
- Fixauxiliary_irq_mode_showdoc (kernel test boot)
---
Documentation/ABI/testing/sysfs-bus-auxiliary| 7 ++ drivers/base/auxiliary.c | 96 ++++++++++++++++++- include/linux/auxiliary_bus.h | 24 ++++-3 files changed, 124 insertions(+), 3 deletions(-)create mode 100644
Documentation/ABI/testing/sysfs-bus-auxiliaryDocumentation/ABI/testing/sysfs-bus-auxiliary new file +5
-0@@ -0,0 +1,7 @@ +What: /sys/bus/auxiliary/devices/.../irqs/ +Date: April, 2024 +Contact: Shay Drory <[email protected]> +Description: + The /sys/devices/.../irqs directory contains a variableset of
+ files, with each file is named as irq number similar to PCI PF
+ or VF's irq number located inmsi_irqsdirectory.drivers/base/auxiliary.c +0
-0@@ -158,6 +158,94 @@* }; */
Quoted 8 lines
Quoted 6 lines
drivers/base/auxiliary.c line 161
Quoted 1 line
drivers/base/auxiliary.c +1
-0+#ifdef CONFIG_SYSFS People really build boxes without sysfs? Ok :(
But if so, why not move this to a whole new file? That would make it simpler to maintain.
sounds good. Will move them to new
sysfs.c
your proposed name combined with the directory would suggest that this is base sysfs for drivers - drivers/base/sysfs.c
please add aux_ prefix, or similar
Quoted 58 lines
Quoted 49 lines
Quoted 49 lines
drivers/base/auxiliary.c +24
-0+struct auxiliary_irq_info { + struct device_attribute sysfs_attr; +}; + +static struct attribute *auxiliary_irq_attrs[] = { + NULL +}; + +static const struct attribute_group auxiliary_irqs_group = { + .name = "irqs", + .attrs = auxiliary_irq_attrs, +}; + +static const struct attribute_group *auxiliary_irqs_groups[] = { + &auxiliary_irqs_group, + NULL +}; + +/** +* auxiliary_device_sysfs_irq_add - add a sysfs entry for the given IRQ +* @auxdev: auxiliary bus device to add the sysfs entry. +* @irq: The associated interrupt number. +* +* This function should be called after auxiliary device have successfully
+ * received the irq.
+ *
+ * Return: zero on success or an error code on failure.
+ */
+intauxiliary_device_sysfs_irq_add(struct auxiliary_device *auxdev, int irq)drivers/base/auxiliary.c +16
-0+{ + struct device *dev = &auxdev->dev; + struct auxiliary_irq_info *info; + int ret; + + info = kzalloc(sizeof(*info), GFP_KERNEL); + if (!info) + return -ENOMEM; + + sysfs_attr_init(&info->sysfs_attr.attr); + info->sysfs_attr.attr.name = kasprintf(GFP_KERNEL, "%d", irq); + if (!info->sysfs_attr.attr.name) { + ret = -ENOMEM; + goto name_err; + } +Quoted 8 lines
Quoted 6 lines
+ ret =
xa_insert(&auxdev->irqs, irq, info, GFP_KERNEL); + if (ret)
+ gotoauxdev_xa_err;
+
+ ret = sysfs_add_file_to_group(&dev->kobj,&info->sysfs_attr.attr, + auxiliary_irqs_group.name);Dynamic attributes are rough, because:
Quoted 2 lines
Your response after "because" is missing.
Can you please elaborate?
you have "complicated" (compared to "nothing" for static attrs) unwinding/error path
Quoted 51 lines
Quoted 34 lines
Quoted 34 lines
+ if (ret)
+ gotosysfs_add_err;drivers/base/auxiliary.c +15
-0+ + return 0; + +sysfs_add_err: + xa_erase(&auxdev->irqs, irq); +auxdev_xa_err: + kfree(info->sysfs_attr.attr.name); +name_err: + kfree(info); + return ret; +} +EXPORT_SYMBOL_GPL (auxiliary_device_sysfs_irq_add); + +/** +* auxiliary_device_sysfs_irq_remove - remove a sysfs entry for the given IRQ
+ * @auxdev: auxiliary bus device to add the sysfs entry.
+ * @irq: the IRQ to remove.
+ *
+ * This function should be called to remove an IRQ sysfs entry.
+ */
+voidauxiliary_device_sysfs_irq_remove(struct auxiliary_device *auxdev, int irq)drivers/base/auxiliary.c +6
-0+{ + struct auxiliary_irq_info *info = xa_load(&auxdev->irqs, irq); + struct device *dev = &auxdev->dev; + + sysfs_remove_file_from_group(&dev->kobj, &info->sysfs_attr.attr, + auxiliary_irqs_group.name);Quoted 8 lines
drivers/base/auxiliary.c
Quoted 5 lines
+
xa_erase(&auxdev->irqs, irq);
+kfree(info->sysfs_attr.attr.name);
+ kfree(info);drivers/base/auxiliary.c +2
-0+} +EXPORT_SYMBOL_GPL (auxiliary_device_sysfs_irq_remove);What is forcing you to remove the irqs after a device is removed from the system?
We are removing the irqs _before_ removing the device. Irqs removal is following the exact mirror of add flow.
Quoted 4 lines
Why not just remove them all automatically? Why would you ever want to remove them after they were added, will they ever actually change over the lifespan of a device?
Quoted 6 lines
IRQs of the SFs are allocated and removed when the resources are created.
for example, devlink reload flow that re-initialize the whole device by releasing and re-allocating new set of IRQs.
Certain driver internal health recovery flow can also trigger similar re-initialize.
I read it as "removing all is what we use 'remove-one' for", I'm correct?
Quoted 36 lines
Quoted 21 lines
Quoted 14 lines
int
auxiliary_device_init(struct auxiliary_device *auxdev); -int__auxiliary_device_add(struct auxiliary_device *auxdev, const char *modname);
-#defineauxiliary_device_add(auxdev)__auxiliary_device_add(auxdev, KBUILD_MODNAME)
+int __auxiliary_device_add(structauxiliary_device*auxdev, const char *modname,
+ boolirqs_sysfs_enable); +#defineauxiliary_device_add(auxdev)__auxiliary_device_add(auxdev, KBUILD_MODNAME, false)
+#defineauxiliary_device_add_with_irqs(auxdev)\
+__auxiliary_device_add(auxdev, KBUILD_MODNAME, true)Ick, no, that way lies madness.
Just keep the original function:
auxiliary_device_add()
as is.Quoted 7 lines
Then, if someone DOES call
auxiliary_device_sysfs_irq_add()then add the irq directory and file as needed then.That way no "norml" paths are messed up and over time, we don't keep having an explosion of combinations of function calls to create an aux device (as we all know, this is NOT going to be the last feature ever added to them...)
Thanks for the suggestion, will change in next version.
Quoted 4 lines
thanks,
greg k-h
Re: [PATCH net-next v6 1/2] driver core: auxiliary bus: show auxiliary device IRQs
Quoted 86 lines · Przemek Kitszel
External email: Use caution opening links or attachments
Quoted 82 lines · Shay Drori
Quoted 79 lines · Greg KH
External email: Use caution opening links or attachments
Quoted 68 lines · Shay Drory
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 58Reviewed-by Parav Pandit <[email protected]>Signed-off-by Shay Drory <[email protected]>---
v5-v6:
- removed concept of shared and exclusive and hence global xarray (Greg)
v4-v5:
- restore global mutex and replacerefcount_twith simple integer (Greg)
v3->4:
- remove global mutex (Przemek)v2->v3:
- fix function declaration in case SYSFS isn't definedv1->v2:
- move #ifdefs fromdrivers/base/auxiliary.ctoinclude/linux/auxiliary_bus.h(Greg)
- useEXPORT_SYMBOL_GPLinstead ofEXPORT_SYMBOL(Greg)
- Fix kzalloc(ref) tokzalloc(*ref)(Simon)
- Add return description inauxiliary_device_sysfs_irq_add()kdoc (Simon)
- Fixauxiliary_irq_mode_showdoc (kernel test boot)
---
Documentation/ABI/testing/sysfs-bus-auxiliary| 7 ++ drivers/base/auxiliary.c | 96
++++++++++++++++++-
include/linux/auxiliary_bus.h | 24 ++++-3 files changed, 124 insertions(+), 3 deletions(-)create mode 100644
Documentation/ABI/testing/sysfs-bus-auxiliaryDocumentation/ABI/testing/sysfs-bus-auxiliary new file +5
-0@@ -0,0 +1,7 @@ +What: /sys/bus/auxiliary/devices/.../irqs/ +Date: April, 2024 +Contact: Shay Drory <[email protected]> +Description: + The /sys/devices/.../irqs directory contains a variableset of
+ files, with each file is named as irq number similar to PCI PF
+ or VF's irq number located inmsi_irqsdirectory.drivers/base/auxiliary.c +0
-0drivers/base/auxiliary.c line 161
Quoted 4 lines
drivers/base/auxiliary.c +1
-0@@ -158,6 +158,94 @@* }; */ +#ifdef CONFIG_SYSFS People really build boxes without sysfs? Ok :(
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
But if so, why not move this to a whole new file? That would make it simpler to maintain.
sounds good. Will move them to new
sysfs.cyour proposed name combined with the directory would suggest that this is base sysfs for drivers -
drivers/base/sysfs.c
please addaux_prefix, or similar
correct, Thanks for the suggestion.
Quoted 60 lines
Quoted 60 lines
Quoted 59 lines
Quoted 47 lines
drivers/base/auxiliary.c +20
-0+struct auxiliary_irq_info { + struct device_attribute sysfs_attr; +}; + +static struct attribute *auxiliary_irq_attrs[] = { + NULL +}; + +static const struct attribute_group auxiliary_irqs_group = { + .name = "irqs", + .attrs = auxiliary_irq_attrs, +}; + +static const struct attribute_group *auxiliary_irqs_groups[] = { + &auxiliary_irqs_group, + NULL +}; + +/** +* auxiliary_device_sysfs_irq_add - add a sysfs entry for the given IRQ
+ * @auxdev: auxiliary bus device to add the sysfs entry.
+ * @irq: The associated interrupt number.
+ *
+ * This function should be called after auxiliary device have successfully
+ * received the irq.
+ *
+ * Return: zero on success or an error code on failure.
+ */
+intauxiliary_device_sysfs_irq_add(struct auxiliary_device *auxdev, int irq)drivers/base/auxiliary.c +12
-0+{ + struct device *dev = &auxdev->dev; + struct auxiliary_irq_info *info; + int ret; + + info = kzalloc(sizeof(*info), GFP_KERNEL); + if (!info) + return -ENOMEM; + + sysfs_attr_init(&info->sysfs_attr.attr); + info->sysfs_attr.attr.name = kasprintf(GFP_KERNEL, "%d", irq); + if (!info->sysfs_attr.attr.name) {drivers/base/auxiliary.c line 212
Quoted 10 lines
drivers/base/auxiliary.c +10
-0+ ret = -ENOMEM; + goto name_err; + } + + ret = xa_insert(&auxdev->irqs, irq, info, GFP_KERNEL); + if (ret) + goto auxdev_xa_err; + + ret = sysfs_add_file_to_group(&dev->kobj, &info->sysfs_attr.attr, + auxiliary_irqs_group.name);Dynamic attributes are rough, because:
Quoted 5 lines
Quoted 2 lines
Your response after "because" is missing.
Can you please elaborate?you have "complicated" (compared to "nothing" for static attrs) unwinding/error path
Dynamic attributes are needed since the number of IRQs per SF is dynamic, one SF can have 10 IRQs and another can have 15 IRQs. In addition, SF is requesting the IRQs on demand, when the SF net-device is opening its channels for example.
Quoted 59 lines
Quoted 52 lines
Quoted 35 lines
Quoted 35 lines
+ if (ret)
+ gotosysfs_add_err;drivers/base/auxiliary.c +15
-0+ + return 0; + +sysfs_add_err: + xa_erase(&auxdev->irqs, irq); +auxdev_xa_err: + kfree(info->sysfs_attr.attr.name); +name_err: + kfree(info); + return ret; +} +EXPORT_SYMBOL_GPL (auxiliary_device_sysfs_irq_add); + +/** +* auxiliary_device_sysfs_irq_remove - remove a sysfs entry for the given IRQ
+ * @auxdev: auxiliary bus device to add the sysfs entry.
+ * @irq: the IRQ to remove.
+ *
+ * This function should be called to remove an IRQ sysfs entry.
+ */
+voidauxiliary_device_sysfs_irq_remove(struct auxiliary_device *auxdev, int irq)drivers/base/auxiliary.c +6
-0+{ + struct auxiliary_irq_info *info = xa_load(&auxdev->irqs, irq); + struct device *dev = &auxdev->dev; + + sysfs_remove_file_from_group(&dev->kobj, &info->sysfs_attr.attr, + auxiliary_irqs_group.name);Quoted 8 lines
drivers/base/auxiliary.c
Quoted 5 lines
+
xa_erase(&auxdev->irqs, irq);
+kfree(info->sysfs_attr.attr.name);
+ kfree(info);drivers/base/auxiliary.c +2
-0+} +EXPORT_SYMBOL_GPL (auxiliary_device_sysfs_irq_remove);What is forcing you to remove the irqs after a device is removed from the system?
We are removing the irqs _before_ removing the device. Irqs removal is following the exact mirror of add flow.
Quoted 4 lines
Why not just remove them all automatically? Why would you ever want to remove them after they were added, will they ever actually change over the lifespan of a device?
Quoted 6 lines
IRQs of the SFs are allocated and removed when the resources are created.
for example, devlink reload flow that re-initialize the whole device by releasing and re-allocating new set of IRQs.
Certain driver internal health recovery flow can also trigger similar re-initialize.
Quoted 3 lines
I read it as "removing all is what we use 'remove-one' for", I'm correct?
I am not sure what you meant here.
what I wanted to say is that SF is requesting and freeing the IRQs one by one and not in bulk.
Quoted 37 lines
Quoted 36 lines
Quoted 21 lines
Quoted 14 lines
int
auxiliary_device_init(struct auxiliary_device *auxdev); -int__auxiliary_device_add(struct auxiliary_device *auxdev, const char *modname);
-#defineauxiliary_device_add(auxdev)__auxiliary_device_add(auxdev, KBUILD_MODNAME)
+int __auxiliary_device_add(structauxiliary_device*auxdev, const char *modname,
+ boolirqs_sysfs_enable); +#defineauxiliary_device_add(auxdev)__auxiliary_device_add(auxdev, KBUILD_MODNAME, false)
+#defineauxiliary_device_add_with_irqs(auxdev)\
+__auxiliary_device_add(auxdev, KBUILD_MODNAME, true)Ick, no, that way lies madness.
Just keep the original function:
auxiliary_device_add()
as is.Quoted 7 lines
Then, if someone DOES call
auxiliary_device_sysfs_irq_add()then add the irq directory and file as needed then.That way no "norml" paths are messed up and over time, we don't keep having an explosion of combinations of function calls to create an aux device (as we all know, this is NOT going to be the last feature ever added to them...)
Thanks for the suggestion, will change in next version.
Quoted 4 lines
thanks,
greg k-h
PATCH v6 2/2 net/mlx5: Expose SFs IRQs
In reply to Shay DroryExpose the sysfs files for the IRQs that the mlx5 PCI SFs are using. These entries are similar to PCI PFs and VFs in 'msi_irqs' directory.
---v5->v6:
- fail IRQ creation in case auxiliary_device_sysfs_irq_add() failed (Parav and Przemek)v2->v3:
- fix mlx5 sfnum SF sysfs
--- drivers/net/ethernet/mellanox/mlx5/core/eq.c | 6 +++--- .../ethernet/mellanox/mlx5/core/irq_affinity.c | 18 +++++++++++++++++- .../ethernet/mellanox/mlx5/core/mlx5_core.h | 6 ++++++ .../net/ethernet/mellanox/mlx5/core/mlx5_irq.h | 12 ++++++++---- .../net/ethernet/mellanox/mlx5/core/pci_irq.c | 12 +++++++++--- .../ethernet/mellanox/mlx5/core/sf/dev/dev.c | 16 +++++++--------- 6 files changed, 50 insertions(+), 20 deletions(-)
drivers/net/ethernet/mellanox/mlx5/core/eq.c +3 -3
@@ -714,7 +714,7 @@ static int create_async_eqs(struct mlx5_core_dev *dev) err1:mlx5_cmd_allowed_opcode (dev,CMD_ALLOWED_OPCODE_ALL );mlx5_eq_notifier_unregister (dev, &table->cq_err_nb); -mlx5_ctrl_irq_release (table->ctrl_irq); +mlx5_ctrl_irq_release (dev, table->ctrl_irq);return err; }
@@ -730,7 +730,7 @@ static void destroy_async_eqs(struct mlx5_core_dev *dev)cleanup_async_eq (dev, &table->cmd_eq,"cmd" );mlx5_cmd_allowed_opcode (dev,CMD_ALLOWED_OPCODE_ALL );mlx5_eq_notifier_unregister (dev, &table->cq_err_nb); -mlx5_ctrl_irq_release (table->ctrl_irq); +mlx5_ctrl_irq_release (dev, table->ctrl_irq); }struct mlx5_eq *mlx5_get_async_eq (struct mlx5_core_dev *dev)
@@ -918,7 +918,7 @@ static int comp_irq_request_sf(struct mlx5_core_dev *dev, u16 vecidx) af_desc.is_managed =1 ;cpumask_copy (&af_desc.mask, cpu_online_mask);cpumask_andnot (&af_desc.mask, &af_desc.mask, &table->used_cpus); - irq =mlx5_irq_affinity_request (pool, &af_desc); + irq =mlx5_irq_affinity_request (dev, pool, &af_desc);if (IS_ERR (irq))return PTR_ERR (irq);
drivers/net/ethernet/mellanox/mlx5/core/irq_affinity.c +17 -1
@@ -112,15 +112,18 @@ irq_pool_find_least_loaded(struct mlx5_irq_pool *pool, const struct cpumask *req/** * mlx5_irq_affinity_request - request an IRQ according to the given mask. +* @dev: mlx5 core device which is requesting the IRQ. * @pool: IRQ pool to request from. * @af_desc: affinity descriptor for this IRQ. * * This function returns a pointer to IRQ, or ERR_PTR in case of error. */ struct mlx5_irq * -mlx5_irq_affinity_request (struct mlx5_irq_pool *pool,struct irq_affinity_desc *af_desc) +mlx5_irq_affinity_request (struct mlx5_core_dev *dev,struct mlx5_irq_pool *pool, +struct irq_affinity_desc *af_desc) {struct mlx5_irq *least_loaded_irq, *new_irq; +int ret;mutex_lock (&pool->lock); least_loaded_irq =irq_pool_find_least_loaded (pool, &af_desc->mask);
@@ -153,6 +156,16 @@ mlx5_irq_affinity_request(struct mlx5_irq_pool *pool, struct irq_affinity_desc * mlx5_irq_read_locked(least_loaded_irq) / MLX5_EQ_REFS_PER_IRQ); unlock:mutex_unlock (&pool->lock); +if (mlx5_irq_pool_is_sf_pool (pool)) { + ret =auxiliary_device_sysfs_irq_add (mlx5_sf_coredev_to_adev (dev), +mlx5_irq_get_irq (least_loaded_irq)); +if (ret) { +mlx5_core_err (dev,"Failed to create sysfs entry for irq %d, ret = %d\n" , +mlx5_irq_get_irq (least_loaded_irq), ret); +mlx5_irq_put (least_loaded_irq); + least_loaded_irq =ERR_PTR (ret); + } + }return least_loaded_irq; }
@@ -164,6 +177,9 @@ void mlx5_irq_affinity_irq_release(struct mlx5_core_dev *dev, struct mlx5_irq *i cpu =cpumask_first (mlx5_irq_get_affinity_mask (irq));synchronize_irq (pci_irq_vector (pool->dev->pdev,mlx5_irq_get_index (irq))); +if (mlx5_irq_pool_is_sf_pool (pool)) +auxiliary_device_sysfs_irq_remove (mlx5_sf_coredev_to_adev (dev), +mlx5_irq_get_irq (irq));if (mlx5_irq_put (irq))if (pool->irqs_per_cpu)cpu_put (pool, cpu);
drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.h +6 -0
@@ -320,6 +320,12 @@ static inline bool mlx5_core_is_sf(const struct mlx5_core_dev *dev)return dev->coredev_type ==MLX5_COREDEV_SF ; } +static inline struct auxiliary_device * +mlx5_sf_coredev_to_adev (struct mlx5_core_dev *mdev) +{ + return container_of(mdev->device, struct auxiliary_device, dev); +} +int mlx5_mdev_init (struct mlx5_core_dev *dev,int profile_idx);void mlx5_mdev_uninit (struct mlx5_core_dev *dev);int mlx5_init_one (struct mlx5_core_dev *dev);
drivers/net/ethernet/mellanox/mlx5/core/mlx5_irq.h +8 -4
@@ -25,7 +25,7 @@ int mlx5_set_msix_vec_count(struct mlx5_core_dev *dev, int devfn,int mlx5_get_default_msix_vec_count (struct mlx5_core_dev *dev,int num_vfs);struct mlx5_irq *mlx5_ctrl_irq_request (struct mlx5_core_dev *dev); -void mlx5_ctrl_irq_release (struct mlx5_irq *ctrl_irq); +void mlx5_ctrl_irq_release (struct mlx5_core_dev *dev,struct mlx5_irq *ctrl_irq);struct mlx5_irq *mlx5_irq_request (struct mlx5_core_dev *dev,u16 vecidx,struct irq_affinity_desc *af_desc,struct cpu_rmap **rmap);
@@ -36,13 +36,15 @@ int mlx5_irq_attach_nb(struct mlx5_irq *irq, struct notifier_block *nb);int mlx5_irq_detach_nb (struct mlx5_irq *irq,struct notifier_block *nb);struct cpumask *mlx5_irq_get_affinity_mask (struct mlx5_irq *irq);int mlx5_irq_get_index (struct mlx5_irq *irq); +int mlx5_irq_get_irq (const struct mlx5_irq *irq);struct mlx5_irq_pool ;#ifdef CONFIG_MLX5_SF struct mlx5_irq *mlx5_irq_affinity_irq_request_auto (struct mlx5_core_dev *dev,struct cpumask *used_cpus,u16 vecidx); -struct mlx5_irq *mlx5_irq_affinity_request (struct mlx5_irq_pool *pool, -struct irq_affinity_desc *af_desc); +struct mlx5_irq * +mlx5_irq_affinity_request (struct mlx5_core_dev *dev,struct mlx5_irq_pool *pool, +struct irq_affinity_desc *af_desc);void mlx5_irq_affinity_irq_release (struct mlx5_core_dev *dev,struct mlx5_irq *irq);#else static inline
@@ -53,7 +55,8 @@ struct mlx5_irq *mlx5_irq_affinity_irq_request_auto(struct mlx5_core_dev *dev, }static inline struct mlx5_irq * -mlx5_irq_affinity_request (struct mlx5_irq_pool *pool,struct irq_affinity_desc *af_desc) +mlx5_irq_affinity_request (struct mlx5_core_dev *dev,struct mlx5_irq_pool *pool, +struct irq_affinity_desc *af_desc) {return ERR_PTR (-EOPNOTSUPP ); }
@@ -61,6 +64,7 @@ mlx5_irq_affinity_request(struct mlx5_irq_pool *pool, struct irq_affinity_desc *static inline void mlx5_irq_affinity_irq_release (struct mlx5_core_dev *dev,struct mlx5_irq *irq) { +mlx5_irq_release_vector (irq); }#endif #endif /* __MLX5_IRQ_H__ */
drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c +9 -3
@@ -367,6 +367,11 @@ struct cpumask *mlx5_irq_get_affinity_mask(struct mlx5_irq *irq)return irq->mask; } +int mlx5_irq_get_irq (const struct mlx5_irq *irq) +{ +return irq->map.virq; +} +int mlx5_irq_get_index (struct mlx5_irq *irq) {return irq->map.index;
@@ -440,11 +445,12 @@ static void _mlx5_irq_release(struct mlx5_irq *irq)/** * mlx5_ctrl_irq_release - release a ctrl IRQ back to the system. +* @dev: mlx5 device that releasing the IRQ. * @ctrl_irq: ctrl IRQ to be released. */ -void mlx5_ctrl_irq_release (struct mlx5_irq *ctrl_irq) +void mlx5_ctrl_irq_release (struct mlx5_core_dev *dev,struct mlx5_irq *ctrl_irq) { -_mlx5_irq_release (ctrl_irq); +mlx5_irq_affinity_irq_release (dev, ctrl_irq); }/**
@@ -473,7 +479,7 @@ struct mlx5_irq *mlx5_ctrl_irq_request(struct mlx5_core_dev *dev)/* Allocate the IRQ in index 0. The vector was already allocated */ irq =irq_pool_request_vector (pool,0 , &af_desc,NULL ); }else { - irq =mlx5_irq_affinity_request (pool, &af_desc); + irq =mlx5_irq_affinity_request (dev, pool, &af_desc); }return irq;
drivers/net/ethernet/mellanox/mlx5/core/sf/dev/dev.c +7 -9
@@ -60,11 +60,6 @@ static const struct attribute_group sf_attr_group = { .attrs = sf_device_attrs, }; -static const struct attribute_group *sf_attr_groups[2 ] = { - &sf_attr_group, -NULL -}; -static void mlx5_sf_dev_release (struct device *device) { struct auxiliary_device *adev = container_of(device, struct auxiliary_device, dev);
@@ -111,7 +106,6 @@ static void mlx5_sf_dev_add(struct mlx5_core_dev *dev, u16 sf_index, u16 fn_id, sf_dev->adev.name =MLX5_SF_DEV_ID_NAME ; sf_dev->adev.dev.release = mlx5_sf_dev_release; sf_dev->adev.dev.parent = &pdev->dev; - sf_dev->adev.dev.groups = sf_attr_groups; sf_dev->sfnum = sfnum; sf_dev->parent_mdev = dev; sf_dev->fn_id = fn_id;
@@ -127,18 +121,22 @@ static void mlx5_sf_dev_add(struct mlx5_core_dev *dev, u16 sf_index, u16 fn_id, goto add_err; } - err =auxiliary_device_add (&sf_dev->adev); + err =auxiliary_device_add_with_irqs (&sf_dev->adev);if (err) {auxiliary_device_uninit (&sf_dev->adev); goto add_err; } + err =devm_device_add_group (&sf_dev->adev.dev, &sf_attr_group); +if (err) + goto add_group_err; + err =xa_insert (&table->devices, sf_index, sf_dev,GFP_KERNEL );if (err) - goto xa_err; + goto add_group_err;return ; -xa_err: +add_group_err:mlx5_sf_dev_remove_aux (dev, sf_dev); add_err: mlx5_core_err(dev, "SF DEV: fail device add for index=%d sfnum=%d err=%d\n",
Signature · 1 line
2.38.1