From: Richard Cheng <icheng@nvidia.com>
To: "Bowman, Terry" <terry.bowman@amd.com>
Cc: dave@stgolabs.net, jic23@kernel.org, dave.jiang@intel.com,
alison.schofield@intel.com, vishal.l.verma@intel.com,
iweiny@kernel.org, ming.li@zohomail.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
kaihengf@nvidia.com, kobak@nvidia.com, newtonl@nvidia.com,
kristinc@nvidia.com
Subject: Re: [PATCH] cxl/port: Unmask AER internal errors for VH endpoints
Date: Tue, 3 Nov 2026 15:25:39 +0800 [thread overview]
Message-ID: <aumLKigtuZ43xRUc@MWDK4CY14F> (raw)
In-Reply-To: <83a62ebc-78b6-4442-a097-566b4a2704a9@amd.com>
On Fri, Oct 30, 2026 at 01:28:14PM +0800, Bowman, Terry wrote:
> On 10/30/2026 4:59 AM, Richard Cheng wrote:
> > CXL protocol errors are reported through PCIe AER internal errors.
> > Unmasking the endpoint's CXL RAS register alone leaves the AER internal
> > errors masked, thus the notification can't reach the Root Port.
> >
> > Unmask AER internal errors during native endpoint RAS setup for VH
> > devices. Allow cxl_port to use pci_aer_unmask_internal_errors() through
> > its module-restricted export.
> >
> > Verified with QEMU mem-data-ecc injection: the Root Port AER interrupt
> > fires, the CXL correctable-error trace is emitted, and the endpoint's
> > CorrIntErr counter increments.
> >
> > Signed-off-by: Richard Cheng <icheng@nvidia.com>
> > ---
> > drivers/cxl/port.c | 7 +++++++
> > drivers/pci/pcie/aer.c | 3 ++-
> > 2 files changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/cxl/port.c b/drivers/cxl/port.c
> > index c48216e5078f..c94a310061b0 100644
> > --- a/drivers/cxl/port.c
> > +++ b/drivers/cxl/port.c
> > @@ -121,6 +121,13 @@ static int cxl_ras_unmask(struct cxl_port *port)
> > orig_val, val);
> > }
> >
> > + /*
> > + * RCH errors are reported by the RCEC. VH endpoints report CXL
> > + * protocol errors as PCIe AER internal errors.
> > + */
> > + if (!is_cxl_restricted(pdev))
> > + pci_aer_unmask_internal_errors(pdev);
> > +
> > return 0;
> > }
> >
>
> Hi Richard,
>
> The unmasking needs to cover the RCD case as well. The RCD AER is used to mask reporting.
> The is_cxl_restricted() gate should be removed so the pci_aer_unmask_internal_errors()
> is called for both the VH and RCD cases.
>
> I confirmed Sashiko's finding that the unmasking will never execute, thanks to this early
> return:
> if (!dev_is_pci(port->uport_dev)) <<== Fails here
> return 0;
> pdev = to_pci_dev(port->uport_dev);
>
> For an endpoint port, port->uport_dev is the cxl_memdev, not a PCI device. So dev_is_pci()
> is false and we return early. The PCI device is `port->uport_dev->parent`.
>
Hi Terry,
Thanks for the headup, and I've also send a patch to fix this issue [1].
And seems like your patch mentioned by Li Ming is already covering
this bug ? if that's the case we can focus on yours, if not I would love
to make the fix in.
Best regards,
Richard Cheng.
[1]: https://lore.kernel.org/linux-cxl/20261103063409.18275-1-icheng@nvidia.com/
> Note, I used base v7.3-rc7. I couldn't find f0c48323b040.
>
> - Terry
>
> > diff --git a/drivers/pci/pcie/aer.c b/drivers/pci/pcie/aer.c
> > index db4f607f889c..94eca22422b7 100644
> > --- a/drivers/pci/pcie/aer.c
> > +++ b/drivers/pci/pcie/aer.c
> > @@ -1287,7 +1287,8 @@ void pci_aer_unmask_internal_errors(struct pci_dev *dev)
> > * Internal errors are too device-specific to enable generally, however for CXL
> > * their behavior is standardized for conveying CXL protocol errors.
> > */
> > -EXPORT_SYMBOL_FOR_MODULES(pci_aer_unmask_internal_errors, "cxl_core");
> > +EXPORT_SYMBOL_FOR_MODULES(pci_aer_unmask_internal_errors,
> > + "cxl_core,cxl_port");
> >
> > #ifdef CONFIG_CXL_RAS
> > bool is_aer_internal_error(struct aer_err_info *info)
> >
> > base-commit: f0c48323b0402349530abc60ea908b5f5f40c395
>
next prev parent reply other threads:[~2026-11-03 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 9:59 Richard Cheng
2026-10-30 18:28 ` Bowman, Terry
2026-11-03 7:25 ` Richard Cheng [this message]
2026-10-30 19:11 ` Li Ming
2026-11-03 7:17 ` Richard Cheng
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=aumLKigtuZ43xRUc@MWDK4CY14F \
--to=icheng@nvidia.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=kaihengf@nvidia.com \
--cc=kobak@nvidia.com \
--cc=kristinc@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=newtonl@nvidia.com \
--cc=terry.bowman@amd.com \
--cc=vishal.l.verma@intel.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
all inboxes | Powered by JetHome®