All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Williams (nvidia)" <djbw@kernel.org>
To: alejandro.lucero-palau@amd.com,  linux-cxl@vger.kernel.org,
	 netdev@vger.kernel.org,  djbw@kernel.org,  edward.cree@amd.com,
	 davem@davemloft.net,  kuba@kernel.org,  pabeni@redhat.com,
	 edumazet@google.com,  dave.jiang@intel.com
Cc: Alejandro Lucero <alucerop@amd.com>
Subject: Re: [PATCH v27 4/5] sfc: obtain and map cxl range using devm_cxl_probe_mem
Date: Tue, 09 Jun 2026 16:30:14 -0700	[thread overview]
Message-ID: <6a28a206bf61a_4fa78100e4@djbw-dev.notmuch> (raw)
In-Reply-To: <20260609215755.8685-5-alejandro.lucero-palau@amd.com>

alejandro.lucero-palau@ wrote:
> From: Alejandro Lucero <alucerop@amd.com>
> 
> Use core API for safely obtain the CXL range linked to an HDM committed
> by the BIOS. Map such a range for being used as the ctpio buffer.
> 
> A potential user space action through sysfs unbinding or core cxl
> modules remove will trigger sfc driver device detachment, with that case
> not racing with this mapping as this is done during driver probe and
> therefore protected with device lock against those user space actions.
> 
> Signed-off-by: Alejandro Lucero <alucerop@amd.com>
> ---
>  drivers/net/ethernet/sfc/efx.c     |  1 +
>  drivers/net/ethernet/sfc/efx_cxl.c | 24 ++++++++++++++++++++++++
>  drivers/net/ethernet/sfc/efx_cxl.h |  3 +++
>  3 files changed, 28 insertions(+)
> 
> diff --git a/drivers/net/ethernet/sfc/efx.c b/drivers/net/ethernet/sfc/efx.c
> index 90ccbe310386..578054c21e79 100644
> --- a/drivers/net/ethernet/sfc/efx.c
> +++ b/drivers/net/ethernet/sfc/efx.c
> @@ -984,6 +984,7 @@ static void efx_pci_remove(struct pci_dev *pci_dev)
>  	efx_fini_io(efx);
>  
>  	probe_data = container_of(efx, struct efx_probe_data, efx);
> +	efx_cxl_exit(probe_data);
>  
>  	pci_dbg(efx->pci_dev, "shutdown successful\n");
>  
> diff --git a/drivers/net/ethernet/sfc/efx_cxl.c b/drivers/net/ethernet/sfc/efx_cxl.c
> index 4d55c08cf2a1..d5766a40e2cf 100644
> --- a/drivers/net/ethernet/sfc/efx_cxl.c
> +++ b/drivers/net/ethernet/sfc/efx_cxl.c
> @@ -18,6 +18,7 @@ int efx_cxl_init(struct efx_probe_data *probe_data)
>  {
>  	struct efx_nic *efx = &probe_data->efx;
>  	struct pci_dev *pci_dev = efx->pci_dev;
> +	struct range cxl_pio_range;
>  	struct efx_cxl *cxl;
>  	u16 dvsec;
>  	int rc;
> @@ -75,9 +76,32 @@ int efx_cxl_init(struct efx_probe_data *probe_data)
>  		return -ENODEV;
>  	}
>  
> +	cxl->cxlmd = devm_cxl_probe_mem(&cxl->cxlds, &cxl_pio_range);
> +	if (IS_ERR(cxl->cxlmd)) {
> +		pci_err(pci_dev, "CXL accel memdev creation failed\n");
> +		return PTR_ERR(cxl->cxlmd);
> +	}
> +
> +	cxl->ctpio_cxl = ioremap_wc(cxl_pio_range.start,
> +				    range_len(&cxl_pio_range));
> +	if (!cxl->ctpio_cxl) {
> +		pci_err(pci_dev, "CXL ioremap region (%pra) failed\n",
> +			&cxl_pio_range);
> +		return -ENOMEM;

Dave caught the iounmap leak, but another concern is since you want to
continue operation if efx_cxl_init() fails then you probably also want
to release the successful attachment to the CXL domain if this happens.

Minor since something else is likely to fail if ioremap is not reliable.

Otherwise this looks good and with those fixed up the Reviewed-by still
stands.

  parent reply	other threads:[~2026-06-09 23:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 21:57 [PATCH v27 0/5] Type2 device basic support alejandro.lucero-palau
2026-06-09 21:57 ` [PATCH v27 1/5] sfc: add cxl support alejandro.lucero-palau
2026-06-09 21:57 ` [PATCH v27 2/5] cxl/sfc: Map cxl regs alejandro.lucero-palau
2026-06-09 21:57 ` [PATCH v27 3/5] cxl/sfc: Initialize dpa without a mailbox alejandro.lucero-palau
2026-06-09 23:24   ` Dan Williams (nvidia)
2026-06-10  6:03     ` Alejandro Lucero Palau
2026-06-09 21:57 ` [PATCH v27 4/5] sfc: obtain and map cxl range using devm_cxl_probe_mem alejandro.lucero-palau
2026-06-09 21:58   ` Dave Jiang
2026-06-10  5:48     ` Alejandro Lucero Palau
2026-06-09 23:30   ` Dan Williams (nvidia) [this message]
2026-06-10  6:10     ` Alejandro Lucero Palau
2026-06-10 13:56       ` Alejandro Lucero Palau
2026-06-09 21:57 ` [PATCH v27 5/5] sfc: support pio mapping based on cxl alejandro.lucero-palau
2026-06-09 22:18   ` Dave Jiang
2026-06-10  5:50     ` Alejandro Lucero Palau

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=6a28a206bf61a_4fa78100e4@djbw-dev.notmuch \
    --to=djbw@kernel.org \
    --cc=alejandro.lucero-palau@amd.com \
    --cc=alucerop@amd.com \
    --cc=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=edward.cree@amd.com \
    --cc=kuba@kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.