From: Davidlohr Bueso <dave@stgolabs.net>
To: vishal.l.verma@intel.com
Cc: linux-cxl@vger.kernel.org, dave@stgolabs.net
Subject: [PATCH -ndctl 0/2] cxl: Support memdev sanitation
Date: Sat, 22 Apr 2023 18:59:18 -0700 [thread overview]
Message-ID: <20230423015920.11384-1-dave@stgolabs.net> (raw)
Hi,
These are the cxl-tool new subcommands for device sanitation for the kernel
side equivalent (currently v4):
https://lore.kernel.org/linux-cxl/20230421092321.12741-1-dave@stgolabs.net/
Obviously the naming of the interfaces are derived from what is currently there
for ndctl. However note that the new cxl wait-sanitize and sanitize-memdev
commands do not rely on pmem security, such as ndctl_dimm_get_security().
However, the kernel does consult pmem security before sending the approving
the operation, so no harm no foul.
This code is also available at:
https://github.com/davidlohr/ndctl/tree/cxl-memdev-sanitation-v1
Thanks!
Davidlohr Bueso (2):
cxl/memdev: Introduce wait-sanitize functionality
cxl/memdev: Introduce sanitize-memdev functionality
Documentation/cxl/cxl-sanitize-memdev.txt | 65 ++++++++++++++++
Documentation/cxl/cxl-wait-sanitize.txt | 39 ++++++++++
Documentation/cxl/lib/libcxl.txt | 2 +
Documentation/cxl/meson.build | 2 +
cxl/builtin.h | 2 +
cxl/cxl.c | 2 +
cxl/lib/libcxl.c | 94 +++++++++++++++++++++++
cxl/lib/libcxl.sym | 2 +
cxl/libcxl.h | 2 +
cxl/memdev.c | 73 ++++++++++++++++++
10 files changed, 283 insertions(+)
create mode 100644 Documentation/cxl/cxl-sanitize-memdev.txt
create mode 100644 Documentation/cxl/cxl-wait-sanitize.txt
--
2.40.0
next reply other threads:[~2023-04-23 2:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 1:59 Davidlohr Bueso [this message]
2023-04-23 1:59 ` [PATCH 1/2] cxl/memdev: Introduce wait-sanitize functionality Davidlohr Bueso
2023-04-26 18:19 ` Verma, Vishal L
2023-04-26 18:25 ` Davidlohr Bueso
2023-04-26 22:01 ` Verma, Vishal L
2023-04-23 1:59 ` [PATCH 2/2] cxl/memdev: Introduce sanitize-memdev functionality Davidlohr Bueso
2023-04-25 15:52 ` 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=20230423015920.11384-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=linux-cxl@vger.kernel.org \
--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