From: Dave Jiang <dave.jiang@intel.com>
To: Wei Hou <wei.hou@scaleflux.com>, Dan Williams <djbw@kernel.org>
Cc: linux-cxl@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jic23@kernel.org>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>, Ming Li <ming.li@zohomail.com>,
linux-kernel@vger.kernel.org, Kobayashi <koba@nvidia.com>,
Kaiheng Feng <kaihengf@nvidia.com>,
Newton Liu <newtonl@nvidia.com>,
Kristin Chen <kristinc@nvidia.com>, Mochs <mochs@nvidia.com>,
Dan Williams <danwilliams@nvidia.com>,
Richard Cheng <icheng@nvidia.com>
Subject: Re: [PATCH v2] cxl/pci: Remove incorrect mbox.valid check in cxl_pci_type3_init_mailbox()
Date: Mon, 29 Jun 2026 09:32:52 -0700 [thread overview]
Message-ID: <211e6322-58e3-4c7d-bc46-2b5acf93cdfb@intel.com> (raw)
In-Reply-To: <20260628155857.239866-1-wei.hou@scaleflux.com>
On 6/28/26 8:58 AM, Wei Hou wrote:
> The driver's design intent is that missing or malformed component
> registers should not prevent mailbox initialization. cxl_pci_probe()
> already reflects this: the CXL_REGLOC_RBI_COMPONENT setup path only
> emits a dev_warn() and continues when component registers are absent,
> rather than returning an error.
>
> The check 'if (!cxlds->reg_map.device_map.mbox.valid)' violates this
> intent and is also technically incorrect for two reasons:
>
> 1. Wrong struct: the MEMDEV register block is enumerated into a local
> variable 'map', not into 'cxlds->reg_map'. The device_map.mbox.valid
> field inside cxlds->reg_map is never written by the MEMDEV probe and
> will always read as zero regardless of actual hardware capability.
>
> 2. Already validated: cxl_pci_setup_regs(CXL_REGLOC_RBI_MEMDEV) calls
> cxl_probe_regs() which explicitly checks mbox.valid and returns
> -ENXIO if the mailbox is absent. If that check passes, the mailbox is
> guaranteed to be present by the time cxl_pci_type3_init_mailbox() is
> called.
>
> The value that the check actually reads is component_map.ras.valid,
> which aliases device_map.mbox.valid in the union. This is populated by
> the COMPONENT probe, not the MEMDEV probe. On devices where the
> component register BAR does not implement a CXL Component Capability
> Array (e.g. certain DCD devices), cxl_probe_component_regs() returns
> early leaving ras.valid=false. Through the union, this makes mbox.valid
> read as false, causing cxl_pci_type3_init_mailbox() to return -ENODEV
> (-19) even though the mailbox hardware is fully functional.
>
> Remove the check. Mailbox presence has already been validated by
> cxl_pci_setup_regs(CXL_REGLOC_RBI_MEMDEV). The presence or absence of
> component registers is irrelevant to mailbox initialization.
>
> Fixes: 8d8081cecfb9 ("cxl: Move mailbox related bits to the same context")
> Reviewed-by: Richard Cheng <icheng@nvidia.com>
> Signed-off-by: Wei Hou <wei.hou@scaleflux.com>
Applied to cxl/next
d79b81893d0c
Next time please post v2 as a separate post instead of having it reply to v1. Thanks.
> ---
> drivers/cxl/pci.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/cxl/pci.c b/drivers/cxl/pci.c
> index bace662dc988..e44e5d209900 100644
> --- a/drivers/cxl/pci.c
> +++ b/drivers/cxl/pci.c
> @@ -691,12 +691,6 @@ static int cxl_pci_type3_init_mailbox(struct cxl_dev_state *cxlds)
> {
> int rc;
>
> - /*
> - * Fail the init if there's no mailbox. For a type3 this is out of spec.
> - */
> - if (!cxlds->reg_map.device_map.mbox.valid)
> - return -ENODEV;
> -
> rc = cxl_mailbox_init(&cxlds->cxl_mbox, cxlds->dev);
> if (rc)
> return rc;
prev parent reply other threads:[~2026-06-29 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 17:03 [PATCH] cxl/pci: Remove incorrect mbox.valid check in cxl_pci_type3_init_mailbox() Wei Hou
2026-06-18 17:18 ` sashiko-bot
2026-06-25 8:05 ` Richard Cheng
2026-06-25 8:10 ` Richard Cheng
2026-06-28 15:58 ` [PATCH v2] " Wei Hou
2026-06-29 5:10 ` Li Ming
2026-06-29 16:32 ` Dave Jiang [this message]
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=211e6322-58e3-4c7d-bc46-2b5acf93cdfb@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=danwilliams@nvidia.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=icheng@nvidia.com \
--cc=ira.weiny@intel.com \
--cc=jic23@kernel.org \
--cc=kaihengf@nvidia.com \
--cc=koba@nvidia.com \
--cc=kristinc@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=mochs@nvidia.com \
--cc=newtonl@nvidia.com \
--cc=vishal.l.verma@intel.com \
--cc=wei.hou@scaleflux.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