From: "Sean V Kelley" <sean.v.kelley@linux.intel.com>
To: "Bjorn Helgaas" <helgaas@kernel.org>
Cc: mj@ucw.cz, linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 2/2] pciutils: Decode Compute eXpress Link DVSEC
Date: Tue, 14 Apr 2020 14:01:53 -0700 [thread overview]
Message-ID: <A89BD01A-195C-40CF-9E06-C30277871086@linux.intel.com> (raw)
In-Reply-To: <20200414203711.GA102808@google.com>
On 14 Apr 2020, at 13:37, Bjorn Helgaas wrote:
> On Mon, Apr 13, 2020 at 08:35:26AM -0700, Sean V Kelley wrote:
>> Compute eXpress Link[1] is a new CPU interconnect created with
>> workload accelerators in mind. The interconnect relies on PCIe
>> electrical and physical interconnect for communication via a Flex Bus
>> port which allows designs to choose between providing PCIe or CXL.
>>
>> This patch introduces basic support for lspci decode of CXL and
>> builds upon the existing Designated Vendor-Specific support in
>> lspci through identification of a Flex Bus capable Vendor ID.
>
> I don't think this is quite right. Isn't the Flex Bus ID the
> "DVSEC ID" (not the "DVSEC Vendor ID")?
Correct. It is not really a Flex Bus ID but really a DVSEC ID. I was
leaning too heavily on the Spec’s wording which stated: “The DVSEC
ID is set to 0x0 to advertise that this is an Flex Bus feature
capability structure.”
I’ll correct. I was trying to note that CXL depends on Flex Bus
capability which is identified through the DVSEC ID. But I confused
things by also mentioning the Vendor ID.
>
>> +static int
>> +is_flexbus_cap(struct device *d, int where)
>> +{
>> + u32 hdr;
>> + u16 w;
>> +
>> + if (!config_fetch(d, where + PCI_DVSEC_HEADER1, 8))
>> + return 0;
>
> And here, I think we need to check the "DVSEC Vendor ID" first, i.e.,
> in the log below, I guess we'd look for the Intel Vendor ID (0x8086).
Agree. Will do.
>
> We can only decode the capability if *both* the DVSEC Vendor ID
> (HEADER1) and the DVSEC ID (HEADER2) match.
Got it.
Thanks,
Sean
>
>> + /* Check for Designated Vendor-Specific Flex Bus Capable ID */
>> + hdr = get_conf_long(d, where + PCI_DVSEC_HEADER2);
>> + w = BITS(hdr, 0, 16);
>> + if (w == PCI_DVSEC_FLEXBUS_ID)
>> + return 1;
>> +
>> + return 0;
>> +}
>> +
>> static void
>> cap_dvsec(struct device *d, int where)
>> {
>> @@ -947,7 +992,10 @@ show_ext_caps(struct device *d, int type)
>> printf("Readiness Time Reporting <?>\n");
>> break;
>> case PCI_EXT_CAP_ID_DVSEC:
>> - cap_dvsec(d, where);
>> + if (is_flexbus_cap(d, where))
>> + cap_cxl(d, where);
>> + else
>> + cap_dvsec(d, where);
>> break;
>> case PCI_EXT_CAP_ID_VF_REBAR:
>> printf("VF Resizable BAR <?>\n");
>
>> + Capabilities: [e00 v1] CXL Designated Vendor-Specific:
>> + CXLCap: Cache+ IO+ Mem+ Mem HW Init+ HDMCount 1
>> Viral-
>> + CXLCtl: Cache+ IO+ Mem- Cache SF Cov 0 Cache SF Gran
>> 0 Cache Clean- Viral-
>> + CXLSta: Viral-
>> + Capabilities: [e38 v1] Device Serial Number
>> 12-34-56-78-90-00-00-00
>
>> +e00: 23 00 81 e3 86 80 80 03 00 00 1f 00 03 00 00 00
>> +e10: 00 00 00 00 00 00 00 00 00 00 00 00 03 01 00 08
>> +e20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> +e30: 00 00 00 00 00 00 00 00 03 00 01 00 00 00 00 90
>> +e40: 78 56 34 12 00 00 00 00 00 00 00 00 00 00 00 00
prev parent reply other threads:[~2020-04-14 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 15:35 [PATCH v4 0/2] pciutils: Add basic decode support for CXL DVSEC Sean V Kelley
2020-04-13 15:35 ` [PATCH v4 1/2] pciutils: Decode available DVSEC details Sean V Kelley
2020-04-13 15:35 ` [PATCH v4 2/2] pciutils: Decode Compute eXpress Link DVSEC Sean V Kelley
2020-04-14 20:37 ` Bjorn Helgaas
2020-04-14 21:01 ` Sean V Kelley [this message]
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=A89BD01A-195C-40CF-9E06-C30277871086@linux.intel.com \
--to=sean.v.kelley@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mj@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).