From: Davidlohr Bueso <dave@stgolabs.net>
To: dave.jiang@intel.com, dan.j.williams@intel.com
Cc: jonathan.cameron@huawei.com, alison.schofield@intel.com,
ira.weiny@intel.com, vishal.l.verma@intel.com,
seven.yi.lee@gmail.com, hch@infradead.org,
a.manzanares@samsung.com, fan.ni@samsung.com, dave@stgolabs.net,
linux-cxl@vger.kernel.org
Subject: [PATCH RFC v2 0/1] cxl/pci: Support Global Persistent Flush (GPF)
Date: Fri, 20 Dec 2024 08:43:36 -0800 [thread overview]
Message-ID: <20241220164337.204900-1-dave@stgolabs.net> (raw)
Hello,
Changes from previous RFC:
- Added dirty shutdown support such that users can tell via Health
if there was any data integrity issues. This patch is still marked
RFC because while in fail (GPF) scenarios that successfully flush the
data the dirty state is cleared, there is no mention of the regular
reboot and shutdown scenarios:
o Is the spec relying on the driver to do so? (currently we can
only reach hot-unplug for this). Regardless, this could use some
clarification in the spec.
o The spec only mentions reboot/shutdown in that it sets the dirty
state upon data integrity issues.
- Limited max T1 timeout to 20 seconds (lockup detector default)
For testing, there are patches out for qemu (dirty shutdown):
https://lore.kernel.org/linux-cxl/20241220160026.204055-3-dave@stgolabs.net/
... as well as those shown in the previous RFC:
https://lore.kernel.org/linux-cxl/20241205082101.1193038-1-dave@stgolabs.net/
Thanks!
Davidlohr Bueso (1):
cxl/pci: Support Global Persistent Flush (GPF)
Documentation/driver-api/cxl/maturity-map.rst | 2 +-
drivers/cxl/core/mbox.c | 17 +++
drivers/cxl/core/pci.c | 104 ++++++++++++++++++
drivers/cxl/core/port.c | 68 ++++++++++++
drivers/cxl/cxl.h | 3 +
drivers/cxl/cxlmem.h | 24 ++++
drivers/cxl/cxlpci.h | 64 +++++++++++
drivers/cxl/pci.c | 97 ++++++++++++++++
8 files changed, 378 insertions(+), 1 deletion(-)
--
2.39.5
next reply other threads:[~2024-12-20 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 16:43 Davidlohr Bueso [this message]
2024-12-20 16:43 ` [PATCH RFC 1/1] cxl/pci: Support Global Persistent Flush (GPF) Davidlohr Bueso
2024-12-20 18:21 ` Ira Weiny
2024-12-21 4:14 ` Davidlohr Bueso
2024-12-23 19:53 ` Jonathan Cameron
2025-01-17 2:28 ` Dan Williams
2025-01-17 7:17 ` Davidlohr Bueso
2025-01-17 7: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=20241220164337.204900-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=fan.ni@samsung.com \
--cc=hch@infradead.org \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=seven.yi.lee@gmail.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