From: Dan Williams <dan.j.williams@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<mahesh.natu@intel.com>, <rafael@kernel.org>
Subject: Re: [ACPI Code First ECN] Enumerate "Inclusive Linear Address Mode" memory-side caches
Date: Fri, 24 May 2024 10:49:54 -0700 [thread overview]
Message-ID: <6650d342bb1c9_6ec3294b@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
In-Reply-To: <20240524123155.00005b0a@Huawei.com>
Jonathan Cameron wrote:
[..]
> > > So should the text say anything about decoder address vs (SRAT / HMAT addressing)
> > > Maybe reasonable to say it's contained and aligned so modulo maths works?
> > > This is a bit odd as HMAT wouldn't typically provide this info, but this addressing
> > > mode already incorporates it sort of...
> >
> > SRAT portrays capacity, HMAT portrays cache and address organization.
> > There is no need for bringing CXL decoder concepts into the HMAT.
>
> Absolutely - avoid any reference to decoders and we are fine.
Well no, because the implications of this addressing mode relative to
CXL decoder settings is the whole reason why "we", Linux CXL community,
are motivated to submit a code-first ECN proposal to explicitly
advertise this addressing mode. The Linux CXL subsystem needs to know
about this addressing mode because of the mismatch between endpoint
decoders and SPA ranges relative to endpoint HPA decode ranges.
Will try to make this point clear because I do not to see a path to
describe the motivation for this ECN without talking about the CXL
problem.
prev parent reply other threads:[~2024-05-24 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 23:00 [ACPI Code First ECN] Enumerate "Inclusive Linear Address Mode" memory-side caches Dan Williams
2024-05-17 16:45 ` Jonathan Cameron
2024-05-17 20:20 ` Dan Williams
2024-05-20 11:53 ` Jonathan Cameron
2024-05-21 15:54 ` Dan Williams
2024-05-23 11:49 ` Jonathan Cameron
2024-05-23 16:36 ` Dan Williams
2024-05-24 11:31 ` Jonathan Cameron
2024-05-24 17:49 ` Dan Williams [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=6650d342bb1c9_6ec3294b@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=mahesh.natu@intel.com \
--cc=rafael@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