From: Dan Williams <dan.j.williams@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: Itaru Kitayama <itaru.kitayama@linux.dev>,
Dave Jiang <dave.jiang@intel.com>, <linux-cxl@vger.kernel.org>
Subject: Re: Internal error: Oops: 0000000096000044 [#11] SMP
Date: Thu, 22 May 2025 11:19:47 -0700 [thread overview]
Message-ID: <682f6ac3e7de3_1626e100a2@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20250522145622.00002633@huawei.com>
Jonathan Cameron wrote:
> On Wed, 21 May 2025 16:34:16 -0700
> Dan Williams <dan.j.williams@intel.com> wrote:
>
> > Itaru Kitayama wrote:
> > > Dave et al.,
> > [..]
> > > Rebuilt the rootfs image and tried today’s cx/next
> > > (6.15.0-rc4-00046-g6eed708a5693) again to boot now I don’t see the
> > > splats, so something I was messing my dev environment sorry about
> > > that.
> > >
> > > CXL utility commands work reasonably now and I can execute meson test
> > > —suite cxl, while most of them still fails due to the HPA allocation
> > > error which makes me wonder as the resource requests are quite modest.
> >
> > So cxl_test_init() just "hopes" that the top of the system physical
> > address space is free to use to emulate CXL windows. That might be an
> > assumption that only works for x86_64, not ARM64. I would double check
> > that this code in cxl_test_init()
> >
> > rc = gen_pool_add(cxl_mock_pool, iomem_resource.end + 1 - SZ_64G,
> > SZ_64G, NUMA_NO_NODE);
> > if (rc)
> > goto err_gen_pool_add;
> >
> > ...is not setting up CXL Windows that overlap with existing resources in
> > that range.
> >
>
> I think there are checks that block use of ranges up there.
>
> Print I'm seeing is
> Hotplug memory [0xfffffff010000000-0xfffffff030000000] exceeds maximum addressable range [0x40000000-0xf80003fffffff]
>
> I think right answer is to use mhp_get_pluggable_range(true); to check
> for limits on the range we can use.
>
> On architectures that don't define arch_get_mappable_range()
> that ends up the as (unsigned long)-1 which I think would work
> though there may be other stuff up there. Maybe min(iomem_resource.end + 1 - SZ_64G,
> mappable_range.end + 1 - SZ_64G)
> or something like that adapted to avoid wrap around.
>
> I haven't yet sanity checked this doesn't break x86 but I think it should
> end up making no difference to the locations on x86.
>
>
> With the below - all 11 tests in ndctl cxl test suite pass for me.
It was whitespace clobbered but after fixing that up and adding #include
<linux/memory_hotplug.h>, it works here, thanks!
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
next prev parent reply other threads:[~2025-05-22 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 8:39 Internal error: Oops: 0000000096000044 [#11] SMP Itaru Kitayama
2025-05-21 15:31 ` Dave Jiang
2025-05-21 20:38 ` Itaru Kitayama
2025-05-21 20:46 ` Dave Jiang
2025-05-21 23:28 ` Itaru Kitayama
2025-05-21 23:34 ` Dan Williams
2025-05-22 13:56 ` Jonathan Cameron
2025-05-22 18:19 ` Dan Williams [this message]
2025-05-22 21:46 ` Itaru Kitayama
2025-05-23 3:28 ` Alison Schofield
2025-05-23 4:56 ` Itaru Kitayama
2025-05-23 5:52 ` Marc Herbert
2025-05-21 15:33 ` Alison Schofield
2025-05-21 15:36 ` Jonathan Cameron
2025-05-21 15:41 ` Alison Schofield
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=682f6ac3e7de3_1626e100a2@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dave.jiang@intel.com \
--cc=itaru.kitayama@linux.dev \
--cc=linux-cxl@vger.kernel.org \
/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