From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Robert Richter <rrichter@amd.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>, <linux-cxl@vger.kernel.org>,
<dave@stgolabs.net>, <alison.schofield@intel.com>,
<vishal.l.verma@intel.com>, <ira.weiny@intel.com>
Subject: Re: [PATCH] cxl: Fix cxl_endpoint_get_perf_coordinate() support for RCH
Date: Tue, 30 Apr 2024 17:54:23 +0100 [thread overview]
Message-ID: <20240430175423.00003589@Huawei.com> (raw)
In-Reply-To: <Zi-RNOZ7OlK6rbuA@rric.localdomain>
On Mon, 29 Apr 2024 14:23:16 +0200
Robert Richter <rrichter@amd.com> wrote:
> On 26.04.24 17:10:07, Dan Williams wrote:
> > Now, that said, if someone can think of why the driver needs to do
> > dynamic performance enumeration for RCH (i.e. a platform BIOS does not
> > populate HMAT), they should speak up now.
It would have to selectively populate HMAT as we'd need the
Generic Port distances anyway. That is an odd corner indeed.
Agreed on disabling it until someone shouts.
>
> I wouldn't stick with that forever as you never know, but for now
> disabling it for RCDs looks good to me to fix this, esp. considering
> we are already at -rc6.
>
> E.g I found in cxl-3.1, 9.11.6 RCD Discovery:
>
> """
> In the future, a
> CXL-aware OS may extract this information directly from the device via
> Table Access DOE.
> """
>
> Thanks,
>
> -Robert
next prev parent reply other threads:[~2024-04-30 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 22:47 [PATCH] cxl: Fix cxl_endpoint_get_perf_coordinate() support for RCH Dave Jiang
2024-04-27 0:10 ` Dan Williams
2024-04-29 12:23 ` Robert Richter
2024-04-30 16:54 ` Jonathan Cameron [this message]
2024-04-29 12:00 ` Robert Richter
2024-04-29 15:56 ` Dave Jiang
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=20240430175423.00003589@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=rrichter@amd.com \
--cc=vishal.l.verma@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).