From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Itaru Kitayama <itaru.kitayama@linux.dev>
Cc: Alison Schofield <alison.schofield@intel.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: ndctl cxl test suite fails in arm64 QEMU
Date: Thu, 13 Mar 2025 09:11:26 +0000 [thread overview]
Message-ID: <20250313091126.000040db@huawei.com> (raw)
In-Reply-To: <4135507A-DECD-4944-8B39-737A7C90D40A@linux.dev>
On Fri, 7 Mar 2025 10:44:23 +0900
Itaru Kitayama <itaru.kitayama@linux.dev> wrote:
> Hi Jonathan, Alison,
>
> > On Feb 28, 2025, at 23:34, Itaru Kitayama <itaru.kitayama@linux.dev> wrote:
> >
> > On Tue, Feb 25, 2025 at 02:40:25PM -0800, Alison Schofield wrote:
> >> On Tue, Feb 25, 2025 at 01:09:57PM +0900, Itaru Kitayama wrote:
> >>> Hi,
> >>>
> >>> Has anyone noticed the ndctl cxl test suite failures I reported below on arm64, QEMU emulation?
> >>>
> >>> https://github.com/pmem/ndctl/issues/278
> >>>
> >>> I’m using Jonathan’s latest CXL capable QEMU [1], and the latest CXL kernel [2].
> >>
> >> Hi Itaru,
> >>
> >> Looking at region.c:size_store() it seems that alloc_hpa() is failing.
> >> (kstrtou64 is arch independent and it works for me with same script &
> >> value)
> >>
> >> Check the dmesg log at the time of the failure. alloc_hpa() may be
> >> emitting a message. (In the run_qemu.sh cmdline add '--cxl-debug')
> >
> > dynamic debug reported this (kernel is without kaslr, today's cxl/next):
> >
> > [ 193.267649] device: 'region4': device_add
> > [ 193.267931] bus: 'cxl': add device region4
> > [ 193.268284] cxl region4: bus: 'cxl': __driver_probe_device: matched device with driver cxl_region
> > [ 193.268333] cxl region4: bus: 'cxl': really_probe: probing driver cxl_region with device
> > [ 193.268401] cxl_region region4: no default pinctrl state
> > [ 193.268482] cxl_region region4: probe with driver cxl_region rejects match -6
> >
> > does the above show the region4 was not added properly? The sysfs
> > entries are there after the out of range failure.
>
> The driver/cxl/core/region.c’s size_store() triggers a sequence of:
>
> alloc_hpa()
> alloc_free_mem_region()
> get_free_mem_region() // with flags set to 0, retruns -ERANGE
>
> While I am looking at the resource core code, do you think this is caused by the old firmware I am using
> when booting QEMU built off of your CXL topic branch? Suggestions are welcome.
Unlikely as I don't think there have been any relevant changes in edk2 for
a long long time.
Jonathan
>
> Itaru.
>
> >
> > Itaru.
> >
> >>
> >> Sounds like Marc is on to something and maybe the KASLR is known
> >> to cause this problem.
> >>
> >> Thanks for posting to this list and send any further questions or
> >> comments. Happy to have you using run_qemu.sh and the cxl tests!
> >>
> >> Alison
> >>
> >>
> >>>
> >>> [1] https://gitlab.com/jic23/qemu/ cxl-2025-02-20
> >>> [2] https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git/
> >>>
> >>> Thanks,
> >>> Itaru.
>
>
>
next prev parent reply other threads:[~2025-03-13 9:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 4:09 ndctl cxl test suite fails in arm64 QEMU Itaru Kitayama
2025-02-25 17:08 ` Marc Herbert
2025-02-25 22:37 ` Itaru Kitayama
2025-02-25 22:48 ` Alison Schofield
2025-02-25 23:53 ` Itaru Kitayama
2025-02-26 18:45 ` Alison Schofield
2025-02-26 22:07 ` Itaru Kitayama
2025-02-27 0:44 ` Itaru Kitayama
2025-02-27 5:31 ` Itaru Kitayama
2025-02-26 19:30 ` Dave Jiang
2025-02-26 22:04 ` Itaru Kitayama
2025-03-01 0:27 ` Marc Herbert
2025-02-26 8:02 ` Itaru Kitayama
2025-02-25 22:40 ` Alison Schofield
2025-02-28 12:15 ` Itaru Kitayama
2025-02-28 14:34 ` Itaru Kitayama
2025-03-07 1:44 ` Itaru Kitayama
2025-03-13 9:11 ` Jonathan Cameron [this message]
2025-03-25 10:14 ` Itaru Kitayama
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=20250313091126.000040db@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@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