From: Dan Williams <dan.j.williams@intel.com>
To: Yee Li <seven.yi.lee@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>
Subject: Re: Is there any plan to support CXL GPF in Linux
Date: Tue, 9 Jul 2024 12:13:48 -0700 [thread overview]
Message-ID: <668d8becca6cf_102cc294a3@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <CALX8JfS5kpY4P0r3QUmDxwoST=d3yR8gzmxK6NSyXr6bRiBo7g@mail.gmail.com>
Hi Yee, please refrain from top-posting [1]
[1]: https://subspace.kernel.org/etiquette.html
Yee Li wrote:
> Dear Christoph,
>
> I agree with you.
> cxl pmem device should process the GPF event well by itself which is sent
> from Host or Switch.
>
> Dear Dan,
>
> ACPI.FADT.PERSISTENT_CPU_CACHES flag is not recognized by Linux.
> Does it mean "cxl pmem flush operations reference the NFIT Platform
> Capabilities"? Or, support the flag and cap in the future.
The Persistent CPU Caches flag is a performance optimization to avoid
CPU cache flushing when the platform is trusted to take care of cache
flushing at power-loss.
Software can force "persistent caches" behavior by:
echo 0 > /sys/block/pmem0/dax/write_cache
From a kernel developer perspective, I feel more comfortable with
userspace making that "go fast at the risk of data-loss" decision. Maybe
after the industry gets more experience with platforms that set that bit
the kernel can default to trusting it, but given the slow roll out of
CXL PMEM devices I think Linux is ok to take a "wait and see" attitude.
At a minimum, if someone wants to draft a patch, it should be a build
time configuration option to trust the FADT.
next prev parent reply other threads:[~2024-07-09 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 8:28 Is there any plan to support CXL GPF in Linux Yee Li
2024-07-09 0:42 ` Dan Williams
2024-07-09 6:06 ` Christoph Hellwig
2024-07-09 7:22 ` Yee Li
2024-07-09 7:35 ` Christoph Hellwig
2024-07-09 9:31 ` Yee Li
2024-07-09 19:13 ` Dan Williams [this message]
2024-07-10 3:46 ` Yee Li
2024-07-09 18:33 ` Dan Williams
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=668d8becca6cf_102cc294a3@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=linux-cxl@vger.kernel.org \
--cc=seven.yi.lee@gmail.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