Linux CXL
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Julien BERAUD <jberaud@sasfermat.com>
Cc: <linux-cxl@vger.kernel.org>, Dan Williams <dan.j.williams@intel.com>
Subject: Re: Prototyping on CXL hardware
Date: Tue, 22 Nov 2022 16:53:31 +0000	[thread overview]
Message-ID: <20221122165331.00006923@Huawei.com> (raw)
In-Reply-To: <40fbb3ef-ccf5-bfbb-675c-861948beba56@sasfermat.com>

On Tue, 22 Nov 2022 10:54:52 +0100
Julien BERAUD <jberaud@sasfermat.com> wrote:

> Hello Everyone,
> 

Hi Julien, Nice to 'meet' you.

> I'm currently trying to prototype with a simple use-case on a CXL type 3 device
> directly connected to a CXL 2.0 capable server.
> 
> Since I have seen many patches being integrated in the mainline kernel, I am 
> running a 6.0.1 release.
> 
> The init phase of the drivers fails with the following trace:
> 
> cxl_mem mem0: at mem0 no parent for dport: pci0000:16
> 
> It occurs at the first iteration of the loop in devm_cxl_enumerate_ports 
> 
> The previous steps have been succeding as far as I know.
> 
> ---------------------------------------------------------------------------------
> So I have a few questions that I hope someone can answer here, I am sorry if they
> sound naive :
> 
> - What is supposed to fill the device's ancestry, and what does it means if there
> is none ?
> 
> - More generally, is a CXL type 3 device directly connected to a CXL capable
> server supposed to initialize correctly on a 6.0.1 kernel or should I use a more
> advanced branch ?

To take a lazy punt in the dark as it end of day here.

Do you have an ACPI CEDT table and required ACPI stuff such as ACPI0017 in DSDT?
Otherwise the root of the created CXL topology will be missing - I haven't checked
the code paths, but that might well give the above result.

There are a few fixes you will want on top of 6.0.1 - but those are all around
region creation I think, so you aren't getting that far.
I've not been tracking progress of those. Dan, what's the current status?

For reference you could take a look at the upstream QEMU (very recent needed as we
had a fix going through on x86).  That should work and gives you something to compare
with when bringing up real hardware.

Jonathan

> 
> 
> Thanks in advance for your answers,
> Julien


  reply	other threads:[~2022-11-22 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22  9:54 Prototyping on CXL hardware Julien BERAUD
2022-11-22 16:53 ` Jonathan Cameron [this message]
2022-11-23  8:39   ` Julien BERAUD

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=20221122165331.00006923@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=dan.j.williams@intel.com \
    --cc=jberaud@sasfermat.com \
    --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