From: Alison Schofield <alison.schofield@intel.com>
To: <alejandro.lucero-palau@amd.com>
Cc: <linux-cxl@vger.kernel.org>, <dan.j.williams@intel.com>,
<dave.jiang@intel.com>, Alejandro Lucero <alucerop@amd.com>
Subject: Re: [PATCH v1 1/3] cxl: support Type2 when initializing cxl_dev_state
Date: Mon, 23 Feb 2026 18:02:53 -0800 [thread overview]
Message-ID: <aZ0GzfdM5i24ymFr@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260223142633.2994082-2-alejandro.lucero-palau@amd.com>
On Mon, Feb 23, 2026 at 02:26:31PM +0000, alejandro.lucero-palau@amd.com wrote:
> From: Alejandro Lucero <alucerop@amd.com>
>
> In preparation for type2 drivers add function and macro for
> differentiating CXL memory expanders (type 3) from CXL device
> accelerators (type 2) helping accel drivers to embed cxl_dev_state
> inside a private struct.
>
> Update type3 driver for using this same initialization.
I've got 2 simple nits that could be fixed-up upon applying,
and one question below.
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
snip
> diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c
> index f547d8ac34c7..ad131f053bf5 100644
> --- a/drivers/cxl/core/memdev.c
> +++ b/drivers/cxl/core/memdev.c
> @@ -656,6 +656,30 @@ static void detach_memdev(struct work_struct *work)
>
> static struct lock_class_key cxl_memdev_key;
>
> +struct cxl_dev_state *_devm_cxl_dev_state_create(struct device *dev,
> + enum cxl_devtype type,
> + u64 serial, u16 dvsec,
> + size_t size, bool has_mbox)
> +{
> + struct cxl_dev_state *cxlds = devm_kzalloc(dev, size, GFP_KERNEL);
> +
> + if (!cxlds)
> + return NULL;
> +
> + cxlds->dev = dev;
> + cxlds->type = type;
> + cxlds->serial = serial;
> + cxlds->cxl_dvsec =dvsec;
Nit one: space around =
> + cxlds->reg_map.host = dev;
> + cxlds->reg_map.resource = CXL_RESOURCE_NONE;
> +
> + if (has_mbox)
> + cxlds->cxl_mbox.host = dev;
> +
> + return cxlds;
> +}
> +EXPORT_SYMBOL_NS_GPL(_devm_cxl_dev_state_create, "CXL");
Why do we name this with leading underscore when we intend to EXPORT it?
Thinking leading underscores are meant for internal helpers?
> +
> static struct cxl_memdev *cxl_memdev_alloc(struct cxl_dev_state *cxlds,
> const struct file_operations *fops,
> const struct cxl_memdev_attach *attach)
> diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
> index e21d744d639b..9daf4bc42692 100644
> --- a/drivers/cxl/cxlmem.h
> +++ b/drivers/cxl/cxlmem.h
> @@ -523,6 +523,37 @@ to_cxl_memdev_state(struct cxl_dev_state *cxlds)
> return container_of(cxlds, struct cxl_memdev_state, cxlds);
> }
>
> +struct cxl_dev_state *_devm_cxl_dev_state_create(struct device *dev,
> + enum cxl_devtype type,
> + u64 serial, u16 dvsec,
> + size_t size, bool has_mbox);
> +
> +/**
> + * cxl_dev_state_create - safely create and cast a cxl dev state embedded in a
> + * driver specific struct.
Nit two: function name is actually devm_cxl_dev_state_create
> + *
> + * @parent: device behind the request
> + * @type: CXL device type
> + * @serial: device identification
> + * @dvsec: dvsec capability offset
> + * @drv_struct: driver struct embedding a cxl_dev_state struct
> + * @member: drv_struct member as cxl_dev_state
> + * @mbox: true if mailbox supported
> + *
> + * Returns a pointer to the drv_struct allocated and embedding a cxl_dev_state
> + * struct initialized.
> + *
> + * Introduced for Type2 driver support.
> + */
> +#define devm_cxl_dev_state_create(parent, type, serial, dvsec, drv_struct, member, mbox) \
> + ({ \
> + static_assert(__same_type(struct cxl_dev_state, \
> + ((drv_struct *)NULL)->member)); \
> + static_assert(offsetof(drv_struct, member) == 0); \
> + (drv_struct *)_devm_cxl_dev_state_create(parent, type, serial, dvsec, \
> + sizeof(drv_struct), mbox); \
> + })
> +
snip
next prev parent reply other threads:[~2026-02-24 2:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 14:26 [PATCH v1 0/3] type2 support preparation alejandro.lucero-palau
2026-02-23 14:26 ` [PATCH v1 1/3] cxl: support Type2 when initializing cxl_dev_state alejandro.lucero-palau
2026-02-24 0:19 ` Dave Jiang
2026-02-24 2:02 ` Alison Schofield [this message]
2026-02-24 16:30 ` Alejandro Lucero Palau
2026-02-23 14:26 ` [PATCH v1 2/3] cxl: export internal structs for external Type2 drivers alejandro.lucero-palau
2026-02-24 0:21 ` Dave Jiang
2026-02-24 2:50 ` Alison Schofield
2026-02-24 16:38 ` Alejandro Lucero Palau
2026-02-24 17:38 ` Alison Schofield
2026-02-25 12:05 ` Alejandro Lucero Palau
2026-02-23 14:26 ` [PATCH v1 3/3] cxl: Move pci generic code alejandro.lucero-palau
2026-02-24 0:27 ` Dave Jiang
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=aZ0GzfdM5i24ymFr@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=alejandro.lucero-palau@amd.com \
--cc=alucerop@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
/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