[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2b5bb8d8-6a7d-4a58-bde7-ce42d0a23f61@amd.com>
Date: Fri, 6 Dec 2024 13:58:23 +0530
From: Raghavendra K T <raghavendra.kt@....com>
To: Dan Williams <dan.j.williams@...el.com>, linux-kernel@...r.kernel.org,
linux-cxl@...r.kernel.org
Cc: bharata@....com, Huang Ying <ying.huang@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>, Davidlohr Bueso <dave@...olabs.net>,
Jonathan Cameron <jonathan.cameron@...wei.com>,
Dave Jiang <dave.jiang@...el.com>,
Alison Schofield <alison.schofield@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>, Ira Weiny <ira.weiny@...el.com>,
Alistair Popple <apopple@...dia.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Bjorn Helgaas <bhelgaas@...gle.com>, Baoquan He <bhe@...hat.com>,
ilpo.jarvinen@...ux.intel.com,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Fontenot Nathan <Nathan.Fontenot@....com>, Wei Huang <wei.huang2@....com>,
regressions@...ts.linux.dev
Subject: Re: [RFC PATCH] resource: Fix CXL node not populated issue
On 12/6/2024 1:20 PM, Dan Williams wrote:
> Raghavendra K T wrote:
>>
[...]
>> B. /proc/iomem
>>
>> $ vimdiff success fail
>>
>> 4050000000-604fffffff : Soft Reserved
>> | 164 4050000000-604fffffff : Soft Reserved
>> 165 4050000000-604fffffff : CXL Window 0
>> | 165 4050000000-604fffffff : CXL Window 0
>> 166 4080000000-5fffffffff : dax1.0
>> |
>> ------------------------------------------------------------------------
>> 167 4080000000-5fffffffff : System RAM (kmem)
>> |
>> --------------------------------------------------------------------
>
> My eyes only know how to read unified diff (diff -u) format. Is this
> saying that in the failure case the System RAM range for dax1.0 is
> missing?
Sorry for that formatting. I realized later.
Yes. dax1.0 missing in the failure case.
Looks like problem is that,
4050000000-604fffffff : Soft Reserved
4050000000-604fffffff : CXL Window 0
4080000000-5fffffffff : dax1.0
4080000000-5fffffffff : System RAM (kmem)
this use case where,
|A<------------->D| CXL window
|..|B<-->C|.......| kmem
B->C range that falls within A->D as in above somehow
not covered after the patch.
Thanks and Regards
- Raghu
Powered by blists - more mailing lists