From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "dave@stgolabs.net" <dave@stgolabs.net>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 1/2] cxl/memdev: Introduce wait-sanitize functionality
Date: Wed, 26 Apr 2023 18:19:38 +0000 [thread overview]
Message-ID: <a1546a23259826fa1e1e469e7d9de902ae914e7e.camel@intel.com> (raw)
In-Reply-To: <20230423015920.11384-2-dave@stgolabs.net>
On Sat, 2023-04-22 at 18:59 -0700, Davidlohr Bueso wrote:
> Add a new cxl_memdev_wait_sanitize() to libcxl to support
> waiting for sanitation operation to be done in the background,
> if any.
>
> This is analogous to 'ndctl wait-overwrite'.
>
> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
> ---
> Documentation/cxl/cxl-wait-sanitize.txt | 35 +++++++++++
> Documentation/cxl/lib/libcxl.txt | 1 +
> Documentation/cxl/meson.build | 1 +
> cxl/builtin.h | 1 +
> cxl/cxl.c | 1 +
> cxl/lib/libcxl.c | 78 +++++++++++++++++++++++++
> cxl/lib/libcxl.sym | 1 +
> cxl/libcxl.h | 1 +
> cxl/memdev.c | 26 +++++++++
> 9 files changed, 145 insertions(+)
> create mode 100644 Documentation/cxl/cxl-wait-sanitize.txt
>
<..>
> diff --git a/cxl/lib/libcxl.sym b/cxl/lib/libcxl.sym
> index 6bc0810152e0..bf7d38f7e6fe 100644
> --- a/cxl/lib/libcxl.sym
> +++ b/cxl/lib/libcxl.sym
> @@ -70,6 +70,7 @@ global:
> cxl_memdev_zero_label;
> cxl_memdev_write_label;
> cxl_memdev_read_label;
> + cxl_memdev_wait_sanitize;
> local:
> *;
> };
Hi Davidlohr,
These mostly look good - just one thing about the symbol script
additions in both this patch and the next one - The different LIBCXL_N
sections in this correspond to a library release, and are used for
libtool versioning.
New symbols in a new release all go together in a new section in this
file. e.g. the pending branch has a 'LIBCXL_5' section for symbols
going in the v77 release (corresponding to kernel v6.3). Assuming these
patches are targeting v78 / v6.4, its new symbols should go in a new
LIBCXL_6 section.
next prev parent reply other threads:[~2023-04-26 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 1:59 [PATCH -ndctl 0/2] cxl: Support memdev sanitation Davidlohr Bueso
2023-04-23 1:59 ` [PATCH 1/2] cxl/memdev: Introduce wait-sanitize functionality Davidlohr Bueso
2023-04-26 18:19 ` Verma, Vishal L [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-07-13 19:54 [PATCH -ndctl v2 0/2] cxl: Support memdev sanitation Davidlohr Bueso
2023-07-13 19:54 ` [PATCH 1/2] cxl/memdev: Introduce wait-sanitize functionality 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=a1546a23259826fa1e1e469e7d9de902ae914e7e.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dave@stgolabs.net \
--cc=linux-cxl@vger.kernel.org \
/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