From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>, <dan.j.williams@intel.com>,
<vishal.l.verma@intel.com>, <fan.ni@samsung.com>,
<a.manzanares@samsung.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 3/6] cxl/mem: Wire up Sanitation support
Date: Wed, 31 May 2023 17:39:45 +0100 [thread overview]
Message-ID: <20230531173945.00006acc@Huawei.com> (raw)
In-Reply-To: <26ea97ef-f69c-b1a1-8db6-7ed62aed8fc0@intel.com>
On Tue, 30 May 2023 16:53:25 -0700
Dave Jiang <dave.jiang@intel.com> wrote:
> On 5/25/23 20:41, Davidlohr Bueso wrote:
> > On Thu, 25 May 2023, Davidlohr Bueso wrote:
> >
> >> Implement support for CXL 3.0 8.2.9.8.5.1 Sanitize. This is done by
> >> adding a security/sanitize' memdev sysfs file, which is poll(2)-capable
> >> for completion. Unlike all other background commands, this is the
> >> only operation that is special and monopolizes the device for long
> >> periods of time.
> >
> > As becomes obvious in the code, this paragraph actually should have
> > been updated: the pollable/read file for the status of sanitation
> > is the security/state.
>
>
> Reviewed-by: Dave Jiang <dave.jiang@intel.com> with above update.
LGTM as well
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
>
>
>
> >
> > Thanks,
> > Davidlohr
>
next prev parent reply other threads:[~2023-05-31 16:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 3:33 [PATCH v5 0/6] cxl: Support device sanitation Davidlohr Bueso
2023-05-26 3:33 ` [PATCH 1/6] cxl/mem: Introduce security state sysfs file Davidlohr Bueso
2023-05-30 23:30 ` Dave Jiang
2023-05-31 16:10 ` Jonathan Cameron
2023-05-31 17:48 ` Fan Ni
2023-05-26 3:33 ` [PATCH 2/6] cxl/mbox: Add sanitation handling machinery Davidlohr Bueso
2023-05-30 23:36 ` Dave Jiang
2023-05-31 16:29 ` Jonathan Cameron
2023-05-31 16:36 ` Jonathan Cameron
2023-05-26 3:33 ` [PATCH 3/6] cxl/mem: Wire up Sanitation support Davidlohr Bueso
2023-05-26 3:41 ` Davidlohr Bueso
2023-05-30 23:53 ` Dave Jiang
2023-05-31 16:39 ` Jonathan Cameron [this message]
2023-05-26 3:33 ` [PATCH 4/6] cxl/test: Add Sanitize opcode support Davidlohr Bueso
2023-05-26 3:33 ` [PATCH 5/6] cxl/mem: Support Secure Erase Davidlohr Bueso
2023-05-30 23:54 ` Dave Jiang
2023-05-31 16:41 ` Jonathan Cameron
2023-06-01 17:24 ` Fan Ni
2023-05-26 3:33 ` [PATCH 6/6] cxl/test: Add Secure Erase opcode support 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=20230531173945.00006acc@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--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