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, a.manzanares@samsung.com,
fan.ni@samsung.com, anisa.su@samsung.com, dave@stgolabs.net,
linux-cxl@vger.kernel.org
Subject: [PATCH v3 0/4] cxl: Dirty shutdown followups
Date: Tue, 18 Feb 2025 19:05:16 -0800 [thread overview]
Message-ID: <20250219030520.237207-1-dave@stgolabs.net> (raw)
Changes from v2:
- remove leftover cxl_gpf_device() declaration
Changes from v1 (https://lore.kernel.org/linux-cxl/20250205040842.1253616-1-dave@stgolabs.net/):
- crated a new cxl_gpf_get_dvsec() helper to share for port and dev gpf (DaveJ)
- renamed cxl_dirty_shutdown_state() to cxl_arm_dirty_shutdown() (DaveJ)
- exported the cxl_gpf_get_dvsec() symbol used outside of core (Yi, DaveJ)
- introduced CXL_INVALID_DIRTY_SHUTDOWN_COUNT (DaveJ)
- use u64 for cxl_nvd->dirty_shutdowns,
- rename to cxl_nvdimm_setup_dirty_tracking() and use return statements (DaveJ)
- picked up review tag in patch 4 (DaveJ)
Hi,
Some followup patches to the GPF work. First two patches are from feedback
provided by DaveJ. The third patch adds a $platform/dirty_shutdown sysfs
attribute to expose the count to userspace. Fourth patch adds support
emulating the set shutdown state command for the mock device.
Applies against the -next branch of cxl.git.
Thanks!
Davidlohr Bueso (4):
cxl/pci: Introduce cxl_gpf_get_dvsec()
cxl/pmem: Rename cxl_dirty_shutdown_state()
cxl/pmem: Export dirty shutdown count via sysfs
tools/testing/cxl: Set Shutdown State support
Documentation/ABI/testing/sysfs-bus-cxl | 12 +++
Documentation/driver-api/cxl/maturity-map.rst | 2 +-
drivers/cxl/core/mbox.c | 25 +++++-
drivers/cxl/core/pci.c | 38 ++++++---
drivers/cxl/cxl.h | 3 +
drivers/cxl/cxlmem.h | 15 +++-
drivers/cxl/pmem.c | 77 +++++++++++++++++--
tools/testing/cxl/test/mem.c | 23 ++++++
8 files changed, 173 insertions(+), 22 deletions(-)
--
2.39.5
next reply other threads:[~2025-02-19 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 3:05 Davidlohr Bueso [this message]
2025-02-19 3:05 ` [PATCH 1/4] cxl/pci: Introduce cxl_gpf_get_dvsec() Davidlohr Bueso
-- strict thread matches above, loose matches on Subject: below --
2025-02-19 6:28 [PATCH v3 0/4] cxl: Dirty shutdown followups Davidlohr Bueso
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=20250219030520.237207-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=anisa.su@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=fan.ni@samsung.com \
--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