public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Andy Gospodarek <andrew.gospodarek@broadcom.com>,
	Aron Silverton <aron.silverton@oracle.com>,
	Dan Williams <dan.j.williams@intel.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	Dave Jiang <dave.jiang@intel.com>,
	"David Ahern" <dsahern@kernel.org>,
	Andy Gospodarek <gospo@broadcom.com>,
	"Christoph Hellwig" <hch@infradead.org>,
	Itay Avraham <itayavr@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	Leonid Bloch <lbloch@nvidia.com>,
	Leon Romanovsky <leonro@nvidia.com>, <linux-cxl@vger.kernel.org>,
	<linux-rdma@vger.kernel.org>, <netdev@vger.kernel.org>,
	Saeed Mahameed <saeedm@nvidia.com>,
	"Nelson, Shannon" <shannon.nelson@amd.com>
Subject: Re: [PATCH v4 01/10] fwctl: Add basic structure for a class subsystem with a cdev
Date: Fri, 7 Feb 2025 15:32:00 -0800	[thread overview]
Message-ID: <67a697f02bc0b_2d1e2948a@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <1-v4-0cf4ec3b8143+4995-fwctl_jgg@nvidia.com>

Jason Gunthorpe wrote:
> Create the class, character device and functions for a fwctl driver to
> un/register to the subsystem.
> 
> A typical fwctl driver has a sysfs presence like:
> 
> $ ls -l /dev/fwctl/fwctl0
> crw------- 1 root root 250, 0 Apr 25 19:16 /dev/fwctl/fwctl0
> 
> $ ls /sys/class/fwctl/fwctl0
> dev  device  power  subsystem  uevent
> 
> $ ls /sys/class/fwctl/fwctl0/device/infiniband/
> ibp0s10f0
> 
> $ ls /sys/class/infiniband/ibp0s10f0/device/fwctl/
> fwctl0/
> 
> $ ls /sys/devices/pci0000:00/0000:00:0a.0/fwctl/fwctl0
> dev  device  power  subsystem  uevent
> 
> Which allows userspace to link all the multi-subsystem driver components
> together and learn the subsystem specific names for the device's
> components.
> 
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
[..]
> +struct fwctl_device *_fwctl_alloc_device(struct device *parent,
> +					 const struct fwctl_ops *ops,
> +					 size_t size);
> +/**
> + * fwctl_alloc_device - Allocate a fwctl
> + * @parent: Physical device that provides the FW interface
> + * @ops: Driver ops to register
> + * @drv_struct: 'struct driver_fwctl' that holds the struct fwctl_device
> + * @member: Name of the struct fwctl_device in @drv_struct
> + *
> + * This allocates and initializes the fwctl_device embedded in the drv_struct.
> + * Upon success the pointer must be freed via fwctl_put(). Returns a 'drv_struct
> + * \*' on success, NULL on error.
> + */
> +#define fwctl_alloc_device(parent, ops, drv_struct, member)               \
> +	({                                                                \
> +		static_assert(__same_type(struct fwctl_device,            \
> +					  ((drv_struct *)NULL)->member)); \
> +		static_assert(offsetof(drv_struct, member) == 0);         \
> +		(drv_struct *)_fwctl_alloc_device(parent, ops,            \
> +						  sizeof(drv_struct));    \
> +	})

I have already suggested someone else copy this approach to context
allocation. What do you think of generalizing this in
include/linux/container_of.h as:

#define container_alloc(core_struct, drv_struct, member, alloc_fn, ...)    \
       ({                                                                 \
               static_assert(__same_type(core_struct,                     \
                                         ((drv_struct *)NULL)->member));  \
               static_assert(offsetof(drv_struct, member) == 0);          \
               (drv_struct *)(alloc_fn)(sizeof(drv_struct), __VA_ARGS__); \
       })

...and then fwctl_alloc_device becomes:

#define fwctl_alloc_device(parent, ops, drv_struct, member) \
	container_alloc(struct fwctl_device, drv_struct, member, \
			_fwctl_alloc_device, parent, ops);

Either way, you can add:

Reviewed-by: Dan Williams <dan.j.williams@intel.com>

  reply	other threads:[~2025-02-07 23:32 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07  0:13 [PATCH v4 00/10] Introduce fwctl subystem Jason Gunthorpe
2025-02-07  0:13 ` [PATCH v4 01/10] fwctl: Add basic structure for a class subsystem with a cdev Jason Gunthorpe
2025-02-07 23:32   ` Dan Williams [this message]
2025-02-07 23:55     ` Jason Gunthorpe
2025-02-08  0:08   ` Dave Jiang
2025-02-07  0:13 ` [PATCH v4 02/10] fwctl: Basic ioctl dispatch for the character device Jason Gunthorpe
2025-02-07 12:59   ` Jonathan Cameron
2025-02-07 13:52     ` Jason Gunthorpe
2025-02-08  0:16   ` Dave Jiang
2025-02-10 15:24     ` Jason Gunthorpe
2025-02-13 12:42   ` Przemek Kitszel
2025-02-13 18:52     ` Jason Gunthorpe
2025-02-07  0:13 ` [PATCH v4 03/10] fwctl: FWCTL_INFO to return basic information about the device Jason Gunthorpe
2025-02-07 13:06   ` Jonathan Cameron
2025-02-07 14:23     ` Jason Gunthorpe
2025-02-08  0:21   ` Dave Jiang
2025-02-07  0:13 ` [PATCH v4 04/10] taint: Add TAINT_FWCTL Jason Gunthorpe
2025-02-07 13:09   ` Jonathan Cameron
2025-02-08  0:24   ` Dave Jiang
2025-02-07  0:13 ` [PATCH v4 05/10] fwctl: FWCTL_RPC to execute a Remote Procedure Call to device firmware Jason Gunthorpe
2025-02-08  0:28   ` Dave Jiang
2025-02-07  0:13 ` [PATCH v4 06/10] fwctl: Add documentation Jason Gunthorpe
2025-02-07 14:42   ` Jonathan Cameron
2025-02-10 15:17     ` Jason Gunthorpe
2025-02-08  0:40   ` Dave Jiang
2025-02-07  0:13 ` [PATCH v4 07/10] fwctl/mlx5: Support for communicating with mlx5 fw Jason Gunthorpe
2025-02-13 13:19   ` Przemek Kitszel
2025-02-13 14:25     ` Leon Romanovsky
2025-02-13 19:18     ` Jason Gunthorpe
2025-02-07  0:13 ` [PATCH v4 08/10] mlx5: Create an auxiliary device for fwctl_mlx5 Jason Gunthorpe
2025-02-07  0:13 ` [PATCH v4 09/10] fwctl/bnxt: Support communicating with bnxt fw Jason Gunthorpe
2025-02-07 14:59   ` Jonathan Cameron
2025-02-07 15:03     ` Jason Gunthorpe
2025-02-07  0:13 ` [PATCH v4 10/10] bnxt: Create an auxiliary device for fwctl_bnxt Jason Gunthorpe
2025-02-07  0:44   ` Jakub Kicinski
2025-02-07  3:17     ` Andy Gospodarek
2025-02-07 12:46       ` Jason Gunthorpe
2025-02-07 15:36       ` Jakub Kicinski
2025-02-07 20:25         ` Saeed Mahameed
2025-02-07 21:51           ` Jakub Kicinski
2025-02-08  1:10             ` Saeed Mahameed
2025-02-08  1:16             ` Jason Gunthorpe
2025-02-08  3:24               ` Andy Gospodarek
2025-02-11  1:04               ` Jakub Kicinski
2025-02-11  7:55                 ` Leon Romanovsky
2025-02-11 14:27                   ` Andy Gospodarek
2025-02-12 14:20                     ` Leon Romanovsky
2025-02-11 18:36                   ` Nelson, Shannon
2025-02-12 13:22                     ` Leon Romanovsky
2025-02-14  1:03                       ` Saeed Mahameed
2025-02-17 12:49                         ` Jiri Pirko
2025-02-17 19:02                           ` Leon Romanovsky
2025-02-11 16:24                 ` David Ahern
2025-02-18 20:05                   ` Jason Gunthorpe
2025-02-18 21:42                     ` David Ahern
2025-02-18 23:31                       ` Jakub Kicinski
2025-02-24 22:34                         ` Saeed Mahameed
2025-02-07 23:29         ` Andy Gospodarek
2025-02-08  0:08           ` Jakub Kicinski
2025-02-07 21:41 ` [PATCH v4 00/10] Introduce fwctl subystem Dan Williams
2025-02-07 21:58 ` Dave Jiang
2025-02-11  9:33   ` Jonathan Cameron
2025-02-13 17:55     ` Jason Gunthorpe
2025-02-13 17:52   ` Jason Gunthorpe
2025-02-12 22:21 ` Zhu Yanjun
2025-02-13  2:30 ` Nelson, Shannon
2025-02-13 18:02   ` Jason Gunthorpe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=67a697f02bc0b_2d1e2948a@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=aron.silverton@oracle.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dave.jiang@intel.com \
    --cc=dsahern@kernel.org \
    --cc=gospo@broadcom.com \
    --cc=hch@infradead.org \
    --cc=itayavr@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=lbloch@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=shannon.nelson@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox