From: Bharata B Rao <bharata@amd.com>
To: Dan Williams <dan.j.williams@intel.com>,
Raghavendra K T <raghavendra.kt@amd.com>,
linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org
Cc: Huang Ying <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Alistair Popple <apopple@nvidia.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>, Baoquan He <bhe@redhat.com>,
ilpo.jarvinen@linux.intel.com,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Fontenot Nathan <Nathan.Fontenot@amd.com>,
Wei Huang <wei.huang2@amd.com>,
regressions@lists.linux.dev
Subject: Re: [RFC PATCH] resource: Fix CXL node not populated issue
Date: Wed, 11 Dec 2024 22:17:11 +0530 [thread overview]
Message-ID: <d8d2c310-2021-431f-adbe-71ad0a17896a@amd.com> (raw)
In-Reply-To: <67594f90a7b87_25073294f0@dwillia2-xfh.jf.intel.com.notmuch>
On 11-Dec-24 2:08 PM, Dan Williams wrote:
> Ah, thanks for that!
>
> So, it turns out Ying's patch is working as advertised. It is traversing
> past the top-level entry of the the iomem_resource topology to discover that a
> Soft Reserved range is described by CXL. Then the expectation is that
> the CXL subsystem parses the topology and registers a dax device.
>
> I missed that detail in my repro because I was not testing the HMEM
> handoff.
>
> Now, the dmesg shows that the CXL subsystem gives up early on the
> CXL devices as they do not appear to be meeting the expecations of a "CXL
> Memory Device" as described by the "PCI Header - Class Code Register
> (Offset 09h)" of the CXL spec.
>
> Specifically these messages:
>
> [ 4.449072] cxl_pci 0000:9f:00.0: registers not found: status mbox memdev
>
> I think this situation is increasingly showing that the pace of
> non-standard quirks being deployed is higher than CXL subsystem is able
> to keep pace.
>
> The immediate workaround to this problem that Linux discovered is to
> disable the cxl_acpi driver. Can you confirm that preventing the
> cxl_acpi driver from loading restores that missing node?
Yes, disabling CONFIG_CXL_ACPI gets the CXL node up with the memory.
Thanks for this workaround.
>
> Longer term the urgency of Nathan's patch [1] needs to be escalated.
>
> [1]: http://lore.kernel.org/20241202155542.22111-1-nathan.fontenot@amd.com
I didn't find that patch helping though with CONFIG_CXL_ACPI kept enabled.
Regards,
Bharata.
next prev parent reply other threads:[~2024-12-11 16:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 11:19 [RFC PATCH] resource: Fix CXL node not populated issue Raghavendra K T
2024-12-02 15:34 ` Andy Shevchenko
2024-12-03 6:01 ` Raghavendra K T
2024-12-03 6:26 ` Huang, Ying
2024-12-03 13:41 ` Andy Shevchenko
[not found] ` <CAAt7c_piFt2UY_OSzdhhr3yFfgMZPgcw2ogtAoVRjgDFGaG_8Q@mail.gmail.com>
2024-12-03 22:07 ` Andy Shevchenko
2024-12-04 2:07 ` Huang, Ying
2024-12-04 3:01 ` Andy Shevchenko
2024-12-04 4:44 ` Raghavendra K T
2024-12-05 5:45 ` Raghavendra K T
2024-12-04 3:55 ` Dan Williams
2024-12-04 4:41 ` Raghavendra K T
2024-12-06 7:50 ` Dan Williams
2024-12-06 8:28 ` Raghavendra K T
2024-12-11 4:44 ` Dan Williams
2024-12-11 6:40 ` Bharata B Rao
2024-12-11 8:38 ` Dan Williams
2024-12-11 16:47 ` Bharata B Rao [this message]
2024-12-12 1:02 ` Raghavendra K T
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=d8d2c310-2021-431f-adbe-71ad0a17896a@amd.com \
--to=bharata@amd.com \
--cc=Nathan.Fontenot@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=apopple@nvidia.com \
--cc=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=raghavendra.kt@amd.com \
--cc=regressions@lists.linux.dev \
--cc=vishal.l.verma@intel.com \
--cc=wei.huang2@amd.com \
--cc=ying.huang@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