From: Gregory Price <gourry@gourry.net>
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: linux-cxl@vger.kernel.org,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] cxl: Allow reprogramming misconfigured hdm decoders
Date: Tue, 29 Apr 2025 22:17:22 -0400 [thread overview]
Message-ID: <aBGIMglj8r5MNAmN@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20250430012915.295136-1-lizhijian@fujitsu.com>
On Wed, Apr 30, 2025 at 09:29:15AM +0800, Li Zhijian wrote:
> During kernel booting, CXL drivers will attempt to construct the CXL region
> according to the pre-programed(firmware provisioning) HDM decoders.
>
> This construction process will fail for some reasons, in this case, the
> userspace cli like ndctl/cxl cannot destroy nor create regions upon the
> existing decoders.
>
> Introuce a new flag CXL_DECODER_F_NEED_RESET tell the driver to reset
> the decoder during `cxl destroy-region regionN`, so that region can be
> create again after that.
>
My best understanding of why this is disallowed is that firmware/bios
programmed decoders need to be locked because there is an assumption
that the platform programmed it that way *for a reason* - and that
changing the programming would break it (cause MCEs for other reasons,
etc).
So the appropriate solution here is for the platform vendor to fix their
firmware.
But I am not a platform people - so I will defer to them on whether my
understanding is correct.
~Gregory
next prev parent reply other threads:[~2025-04-30 2:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 1:29 [RFC PATCH] cxl: Allow reprogramming misconfigured hdm decoders Li Zhijian
2025-04-30 2:17 ` Gregory Price [this message]
2025-04-30 3:24 ` Zhijian Li (Fujitsu)
2025-04-30 8:42 ` Alejandro Lucero Palau
2025-05-07 6:42 ` Zhijian Li (Fujitsu)
2025-05-07 11:10 ` Alejandro Lucero Palau
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=aBGIMglj8r5MNAmN@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhijian@fujitsu.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