From: Gregory Price <gourry@gourry.net>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Vishal Aslot <vaslot@nvidia.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Li Ming <ming.li@zohomail.com>,
Peter Zijlstra <peterz@infradead.org>,
"open list:COMPUTE EXPRESS LINK (CXL)"
<linux-cxl@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/2] cxl_test: enable zero sized decoders under hb0
Date: Wed, 11 Feb 2026 10:04:41 -0500 [thread overview]
Message-ID: <aYyaicFMzfsd8eSq@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <aPeSqjqU6BH9gvcw@gourry-fedora-PF4VCD3F>
On Tue, Oct 21, 2025 at 10:03:22AM -0400, Gregory Price wrote:
>
> Re commit order - Vishal said they do post-lock order
> https://lore.kernel.org/linux-cxl/aOP3Kr3jHLWOydRp@gourry-fedora-PF4VCD3F/
>
> Post-lock order
> [programmable] [zero-lock] [zero-lock] ... [zero-lock]
>
> Pre-lock order:
> [zero-lock] [zero-lock] ... [zero-lock] [programmable]
>
> My reading of the spec suggests that Post-lock ordering is *not legal*,
> and would suggest the software has deviated from the spec - which does
> not allow for size-zero decoders to ignore commit order.
>
Revisiting this - it might be reasonable to allow post-lock ordering if
*all* decoders in beyond the programmable one are zero-locked.
Seems ok? Thoughts?
~Gregory
next prev parent reply other threads:[~2026-02-11 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 2:40 [PATCH v1 0/2] Support zero-sized decoders Vishal Aslot
2025-10-15 2:40 ` [PATCH v1 1/2] cxl_test: enable zero sized decoders under hb0 Vishal Aslot
2025-10-15 15:38 ` Dave Jiang
2025-10-20 7:09 ` Alison Schofield
2025-10-20 14:19 ` Gregory Price
2025-10-20 19:30 ` Alison Schofield
2025-10-20 21:22 ` Dave Jiang
2025-10-21 14:03 ` Gregory Price
2026-02-11 15:04 ` Gregory Price [this message]
2026-02-11 15:59 ` Gregory Price
2025-10-15 2:40 ` [PATCH v1 2/2] cxl: Allow zero sized HDM decoders Vishal Aslot
2025-10-15 16:38 ` Dave Jiang
2025-10-20 6:46 ` Alison Schofield
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=aYyaicFMzfsd8eSq@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--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=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=peterz@infradead.org \
--cc=vaslot@nvidia.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