From: "Martin Mareš" <mj@ucw.cz>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Kobayashi,Daisuke" <kobayashi.da-06@fujitsu.com>,
linux-cxl@vger.kernel.org, y-goto@fujitsu.com,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 3/3] Add function to display cxl1.1 device link status
Date: Sun, 31 Mar 2024 03:03:57 +0200 [thread overview]
Message-ID: <mj+md-20240331.010245.99093.nikam@ucw.cz> (raw)
In-Reply-To: <660767abc418d_19e0294c7@dwillia2-mobl3.amr.corp.intel.com.notmuch>
Hello!
> > Does it make sense to look up CXL RCD information for all PCIe devices of type
> > PCI_EXP_TYPE_ROOT_INT_EP? Shouldn't it be done only for devices with the CXL
> > capability?
>
> I think so, would this fit more naturally in pci_scan_caps() with a new
> scan for DVSEC caps ("PCI_EXT_CAP_ID_DVSEC" in Linux). However, isn't
> the trouble that this needs a DVSEC scan for CXL to know it needs to go
> back and fill in details that normally in appear in the base PCIe
> capability scan?
I would prefer to display all CXL stuff together (i.e., when showing the
DVSEC caps). Is there any reason not to?
Martin
next prev parent reply other threads:[~2024-03-31 1:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 8:05 [PATCH v3 0/3] Display cxl1.1 device link status Kobayashi,Daisuke
2024-03-12 8:05 ` [PATCH v3 1/3] Add sysfs attribute for CXL 1.1 " Kobayashi,Daisuke
2024-03-26 19:51 ` Dan Williams
2024-03-28 1:47 ` Daisuke Kobayashi (Fujitsu)
2024-04-03 9:40 ` Daisuke Kobayashi (Fujitsu)
2024-04-05 8:31 ` Daisuke Kobayashi (Fujitsu)
2024-04-08 21:43 ` Dan Williams
2024-04-09 4:55 ` Daisuke Kobayashi (Fujitsu)
2024-04-05 17:25 ` Jonathan Cameron
2024-04-08 21:32 ` Dan Williams
2024-04-09 14:59 ` Bjorn Helgaas
2024-04-09 15:00 ` Bjorn Helgaas
2024-03-12 8:05 ` [PATCH v3 2/3] Remove conditional branch that is not suitable for cxl1.1 devices Kobayashi,Daisuke
2024-03-26 20:00 ` Dan Williams
2024-03-27 8:26 ` Daisuke Kobayashi (Fujitsu)
2024-03-12 8:05 ` [PATCH v3 3/3] Add function to display cxl1.1 device link status Kobayashi,Daisuke
2024-03-26 20:05 ` Dan Williams
2024-03-27 8:27 ` Daisuke Kobayashi (Fujitsu)
2024-03-29 22:23 ` Martin Mareš
2024-03-30 1:15 ` Dan Williams
2024-03-31 1:03 ` Martin Mareš [this message]
2024-04-01 17:47 ` Dan Williams
2024-04-02 7:09 ` Daisuke Kobayashi (Fujitsu)
2024-03-25 4:49 ` [PATCH v3 0/3] Display " Daisuke Kobayashi (Fujitsu)
2024-03-26 19:15 ` Dan Williams
2024-03-27 8:24 ` 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=mj+md-20240331.010245.99093.nikam@ucw.cz \
--to=mj@ucw.cz \
--cc=dan.j.williams@intel.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