From: Gregory Price <gourry@gourry.net>
To: Richard Cheng <icheng@nvidia.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
dave@stgolabs.net, jic23@kernel.org, alison.schofield@intel.com,
vishal.l.verma@intel.com, djbw@kernel.org, iweiny@kernel.org,
ming.li@zohomail.com, rrichter@amd.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
sreddym@nvidia.com, smadhavan@nvidia.com, kaihengf@nvidia.com,
kobak@nvidia.com, newtonl@nvidia.com, kristinc@nvidia.com,
mochs@nvidia.com
Subject: Re: [PATCH] cxl/region: Restore passthrough decoder enable on region re-assembly
Date: Wed, 5 Aug 2026 02:55:10 -0400 [thread overview]
Message-ID: <anLd5Ln3VvDtE0Yf@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <anLVILs6MNR2lx5i@MWDK4CY14F>
On Wed, Aug 05, 2026 at 02:21:05PM +0800, Richard Cheng wrote:
> On Tue, Jul 28, 2026 at 07:25:09AM +0800, Dave Jiang wrote:
>
> So I re-tested those operations on v7.0-rc2 kernel without the patch, we find out
>
> 0a70b7cd397e ("cxl: Test CXL_DECODER_F_LOCK as a bitmask")
>
> This patch is not needed, and Gregory is right that intermediate decoders should stay locked and
> not have F_ENABLE cleared on teardown.
>
Makes sense to me, it will look a little funky but auto decoders already
got that funk all over them so it is what it is. :]
~Gregory
prev parent reply other threads:[~2026-08-05 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 10:37 [PATCH] cxl/region: Restore passthrough decoder enable on region re-assembly Richard Cheng
2026-07-27 20:25 ` Dave Jiang
2026-07-28 3:03 ` Richard Cheng
2026-07-28 4:14 ` Gregory Price
2026-07-31 9:13 ` Richard Cheng
2026-07-28 14:25 ` Dave Jiang
2026-08-05 6:21 ` Richard Cheng
2026-08-05 6:55 ` Gregory Price [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=anLd5Ln3VvDtE0Yf@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=icheng@nvidia.com \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=kaihengf@nvidia.com \
--cc=kobak@nvidia.com \
--cc=kristinc@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=mochs@nvidia.com \
--cc=newtonl@nvidia.com \
--cc=rrichter@amd.com \
--cc=smadhavan@nvidia.com \
--cc=sreddym@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