public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: KobayashiDaisuke <kobayashi.da-06@fujitsu.com>
Cc: <linux-pci@vger.kernel.org>, <linux-cxl@vger.kernel.org>,
	<y-goto@fujitsu.com>
Subject: Re: [RFC PATCH 0/3] lspci: Display cxl1.1 device link status
Date: Tue, 9 Jan 2024 15:57:55 +0000	[thread overview]
Message-ID: <20240109155755.0000087b@Huawei.com> (raw)
In-Reply-To: <20231220050738.178481-1-kobayashi.da-06@fujitsu.com>

On Wed, 20 Dec 2023 14:07:35 +0900
KobayashiDaisuke <kobayashi.da-06@fujitsu.com> wrote:

> Hello.
> 
> This patch series adds a feature to lspci that displays the link status
> of the CXL1.1 device.
> 
> CXL devices are extensions of PCIe. Therefore, from CXL2.0 onwards,
> the link status can be output in the same way as traditional PCIe.
> However, unlike devices from CXL2.0 onwards, CXL1.1 requires a
> different method to obtain the link status from traditional PCIe.
> This is because the link status of the CXL1.1 device is not mapped
> in the configuration space (as per cxl3.0 specification 8.1).
> Instead, the configuration space containing the link status is mapped
> to the memory mapped register region (as per cxl3.0 specification 8.2,
> Table 8-18). Therefore, the current lspci has a problem where it does
> not display the link status of the CXL1.1 device. 
> This patch solves these issues.
> 
> The method of acquisition is in the order of obtaining the device UID,
> obtaining the base address from CEDT, and then obtaining the link
> status from memory mapped register. Considered outputting with the cxl
> command due to the scope of the CXL specification, but devices from
> CXL2.0 onwards can be output in the same way as traditional PCIe.
> Therefore, it would be better to make the lspci command compatible with
> the CXL1.1 device for compatibility reasons.
> 
> I look forward to any comments you may have.
Yikes. 

My gut feeling is that you shouldn't need to do this level of hackery.

If we need this information to be exposed to tooling then we should
add support to the kernel to export it somewhere in sysfs and read that
directly.  Do we need it to be available in absence of the CXL driver
stack? 

Jonathan
> 
> KobayashiDaisuke (3):
>   Add function to display cxl1.1 device link status
>   Implement a function to get cxl1.1 device uid
>   Implement a function to get a RCRB Base address
> 
>  ls-caps.c | 216 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  lspci.h   |  35 +++++++++
>  2 files changed, 251 insertions(+)
> 


  parent reply	other threads:[~2024-01-09 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20  5:07 [RFC PATCH 0/3] lspci: Display cxl1.1 device link status KobayashiDaisuke
2023-12-20  5:07 ` [RFC PATCH 1/3] Add function to display " KobayashiDaisuke
2023-12-20  5:07 ` [RFC PATCH 2/3] Implement a function to get cxl1.1 device uid KobayashiDaisuke
2023-12-20  5:07 ` [RFC PATCH 3/3] Implement a function to get a RCRB Base address KobayashiDaisuke
2024-01-09 15:57 ` Jonathan Cameron [this message]
2024-01-11  1:11   ` [RFC PATCH 0/3] lspci: Display cxl1.1 device link status Dan Williams
2024-01-12 11:24     ` Jonathan Cameron
2024-01-15  9:09       ` Daisuke Kobayashi (Fujitsu)
2024-01-16 21:29         ` Dan Williams
2024-01-17  9:23           ` Daisuke Kobayashi (Fujitsu)
2024-01-17 12:10 ` Martin Mareš
2024-01-18  5:07   ` Daisuke Kobayashi (Fujitsu)

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=20240109155755.0000087b@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=kobayashi.da-06@fujitsu.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=y-goto@fujitsu.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