From: Dan Williams <dan.j.williams@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>, <dan.j.williams@intel.com>
Cc: <dave.jiang@intel.com>, <vishal.l.verma@intel.com>,
<Jonathan.Cameron@huawei.com>, <fan.ni@samsung.com>,
<a.manzanares@samsung.com>, <dave@stgolabs.net>,
<linux-cxl@vger.kernel.org>
Subject: RE: [PATCH 3/7] cxl/mbox: Add sanitation handling machinery
Date: Sun, 25 Jun 2023 15:13:15 -0700 [thread overview]
Message-ID: <6498bbfb35c6f_2ed72947a@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20230612181038.14421-4-dave@stgolabs.net>
Davidlohr Bueso wrote:
> Sanitation is by definition a device-monopolizing operation, and thus
> the timeslicing rules for other background commands do not apply.
> As such handle this special case asynchronously and return immediately.
> Subsequent changes will allow completion to be pollable from userspace
> via a sysfs file interface.
>
> For devices that don't support interrupts for notifying background
> command completion, self-poll with the caveat that the poller can
> be out of sync with the ready hardware, and therefore care must be
> taken to not allow any new commands to go through until the poller
> sees the hw completion. The poller takes the mbox_mutex to stabilize
> the flagging, minimizing any runtime overhead in the send path to
> check for 'sanitize_tmo' for uncommon poll scenarios.
>
> The irq case is much simpler as hardware will serialize/error
> appropriately.
Some minor things to fixup below, if this is all I find I can likely
handle this on applying:
>
> Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
> ---
> drivers/cxl/core/memdev.c | 10 +++++
> drivers/cxl/cxlmem.h | 7 ++++
> drivers/cxl/pci.c | 77 +++++++++++++++++++++++++++++++++++++--
> 3 files changed, 91 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c
> index 1bbb7e39fc93..834f418b6bcb 100644
> --- a/drivers/cxl/core/memdev.c
> +++ b/drivers/cxl/core/memdev.c
> @@ -460,11 +460,21 @@ void clear_exclusive_cxl_commands(struct cxl_dev_state *cxlds, unsigned long *cm
> }
> EXPORT_SYMBOL_NS_GPL(clear_exclusive_cxl_commands, CXL);
>
> +static void cxl_memdev_security_shutdown(struct device *dev)
> +{
> + struct cxl_memdev *cxlmd = to_cxl_memdev(dev);
> + struct cxl_dev_state *cxlds = cxlmd->cxlds;
> +
> + if (cxlds->security.poll)
> + cancel_delayed_work_sync(&cxlds->security.poll_dwork);
> +}
> +
> static void cxl_memdev_shutdown(struct device *dev)
> {
> struct cxl_memdev *cxlmd = to_cxl_memdev(dev);
>
> down_write(&cxl_memdev_rwsem);
> + cxl_memdev_security_shutdown(dev);
> cxlmd->cxlds = NULL;
> up_write(&cxl_memdev_rwsem);
> }
> diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
> index 091f1200736b..3a9df1044144 100644
> --- a/drivers/cxl/cxlmem.h
> +++ b/drivers/cxl/cxlmem.h
> @@ -264,9 +264,15 @@ struct cxl_poison_state {
> * struct cxl_security_state - Device security state
> *
> * @state: state of last security operation
> + * @poll: polling for sanitation is enabled, device has no mbox irq support
> + * @poll_tmo_secs: polling timeout
> + * @poll_dwork: polling work item
> */
> struct cxl_security_state {
> unsigned long state;
> + bool poll;
> + int poll_tmo_secs;
> + struct delayed_work poll_dwork;
> };
>
> /**
> @@ -379,6 +385,7 @@ enum cxl_opcode {
> CXL_MBOX_OP_GET_SCAN_MEDIA_CAPS = 0x4303,
> CXL_MBOX_OP_SCAN_MEDIA = 0x4304,
> CXL_MBOX_OP_GET_SCAN_MEDIA = 0x4305,
> + CXL_MBOX_OP_SANITIZE = 0x4400,
> CXL_MBOX_OP_GET_SECURITY_STATE = 0x4500,
> CXL_MBOX_OP_SET_PASSPHRASE = 0x4501,
> CXL_MBOX_OP_DISABLE_PASSPHRASE = 0x4502,
> diff --git a/drivers/cxl/pci.c b/drivers/cxl/pci.c
> index 4b2575502f49..c92eab55a5a7 100644
> --- a/drivers/cxl/pci.c
> +++ b/drivers/cxl/pci.c
> @@ -115,18 +115,52 @@ static bool cxl_mbox_background_complete(struct cxl_dev_state *cxlds)
>
> static irqreturn_t cxl_pci_mbox_irq(int irq, void *id)
> {
> + u64 reg;
> + u16 opcode;
> struct cxl_dev_id *dev_id = id;
> struct cxl_dev_state *cxlds = dev_id->cxlds;
>
> if (!cxl_mbox_background_complete(cxlds))
> return IRQ_NONE;
>
> - /* short-circuit the wait in __cxl_pci_mbox_send_cmd() */
> - rcuwait_wake_up(&cxlds->mbox_wait);
> + reg = readq(cxlds->regs.mbox + CXLDEV_MBOX_BG_CMD_STATUS_OFFSET);
> + opcode = FIELD_GET(CXLDEV_MBOX_BG_CMD_COMMAND_OPCODE_MASK, reg);
> + if (opcode == CXL_MBOX_OP_SANITIZE) {
> + dev_dbg(cxlds->dev, "Sanitation operation ended\n");
> + } else {
> + /* short-circuit the wait in __cxl_pci_mbox_send_cmd() */
> + rcuwait_wake_up(&cxlds->mbox_wait);
Just a question, is there any harm in awaking this even though nothing
is waiting? I.e. just wondering if this has functional purpose or is
just for cleanliness?
> + }
>
> return IRQ_HANDLED;
> }
>
> +/*
> + * Sanitation operation polling mode.
> + */
> +static void cxl_mbox_sanitize_work(struct work_struct *work)
> +{
> + struct cxl_dev_state *cxlds;
> +
> + cxlds = container_of(work,
> + struct cxl_dev_state, security.poll_dwork.work);
> +
> + mutex_lock(&cxlds->mbox_mutex);
> + if (cxl_mbox_background_complete(cxlds)) {
> + cxlds->security.poll_tmo_secs = 0;
> + put_device(cxlds->dev);
> +
> + dev_dbg(cxlds->dev, "Sanitation operation ended\n");
> + } else {
> + int timeout = cxlds->security.poll_tmo_secs + 10;
> +
> + cxlds->security.poll_tmo_secs = min(15 * 60, timeout);
> + queue_delayed_work(system_wq, &cxlds->security.poll_dwork,
> + timeout * HZ);
> + }
> + mutex_unlock(&cxlds->mbox_mutex);
> +}
> +
> /**
> * __cxl_pci_mbox_send_cmd() - Execute a mailbox command
> * @cxlds: The device state to communicate with.
> @@ -187,6 +221,16 @@ static int __cxl_pci_mbox_send_cmd(struct cxl_dev_state *cxlds,
> return -EBUSY;
> }
>
> + /*
> + * With sanitize polling, hardware might be done and the poller still
> + * not be in sync. Ensure no new command comes in until so. Keep the
> + * hardware semantics and only allow device health status.
> + */
> + if (unlikely(cxlds->security.poll_tmo_secs > 0)) {
CPUs and compilers do a decent job at likely/unlikely branch prediction,
and given mailbox operations are a slow path I can not imagine this
unlikely() annotation makes any measurable difference.
> + if (mbox_cmd->opcode != CXL_MBOX_OP_GET_HEALTH_INFO)
> + return -EBUSY;
> + }
> +
> cmd_reg = FIELD_PREP(CXLDEV_MBOX_CMD_COMMAND_OPCODE_MASK,
> mbox_cmd->opcode);
> if (mbox_cmd->size_in) {
> @@ -235,11 +279,34 @@ static int __cxl_pci_mbox_send_cmd(struct cxl_dev_state *cxlds,
> */
> if (mbox_cmd->return_code == CXL_MBOX_CMD_RC_BACKGROUND) {
> u64 bg_status_reg;
> - int i, timeout = mbox_cmd->poll_interval_ms;
> + int i, timeout;
> +
> + /*
> ++ * Sanitation is a special case which monopolizes the device
^ extra '+' character?
> + * and cannot be timesliced. Handle asynchronously instead,
> + * and allow userspace to poll(2) for completion.
> + */
> + if (mbox_cmd->opcode == CXL_MBOX_OP_SANITIZE) {
> + if (cxlds->security.poll_tmo_secs != -1) {
> + /* hold the device throughout */
> + get_device(cxlds->dev);
> +
> + /* give first timeout a second */
> + timeout = 1;
> + cxlds->security.poll_tmo_secs = timeout;
> + queue_delayed_work(system_wq,
> + &cxlds->security.poll_dwork,
> + timeout * HZ);
> + }
> +
> + dev_dbg(dev, "Sanitation operation started\n");
> + goto success;
> + }
>
> dev_dbg(dev, "Mailbox background operation (0x%04x) started\n",
> mbox_cmd->opcode);
>
> + timeout = mbox_cmd->poll_interval_ms;
> for (i = 0; i < mbox_cmd->poll_count; i++) {
> if (rcuwait_wait_event_timeout(&cxlds->mbox_wait,
> cxl_mbox_background_complete(cxlds),
> @@ -270,6 +337,7 @@ static int __cxl_pci_mbox_send_cmd(struct cxl_dev_state *cxlds,
> return 0; /* completed but caller must check return_code */
> }
>
> +success:
> /* #7 */
> cmd_reg = readq(cxlds->regs.mbox + CXLDEV_MBOX_CMD_OFFSET);
> out_len = FIELD_GET(CXLDEV_MBOX_CMD_PAYLOAD_LENGTH_MASK, cmd_reg);
> @@ -382,6 +450,9 @@ static int cxl_pci_setup_mailbox(struct cxl_dev_state *cxlds)
> }
>
> mbox_poll:
> + cxlds->security.poll = true;
> + INIT_DELAYED_WORK(&cxlds->security.poll_dwork, cxl_mbox_sanitize_work);
> +
> dev_dbg(cxlds->dev, "Mailbox interrupts are unsupported");
> return 0;
> }
> --
> 2.41.0
>
next prev parent reply other threads:[~2023-06-25 22:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 18:10 [PATCH v6 0/7] cxl: Support device sanitation Davidlohr Bueso
2023-06-12 18:10 ` [PATCH 1/7] cxl/mbox: Allow for IRQ_NONE case in the isr Davidlohr Bueso
2023-06-13 12:49 ` Jonathan Cameron
2023-06-13 18:11 ` Dave Jiang
2023-06-12 18:10 ` [PATCH 2/7] cxl/mem: Introduce security state sysfs file Davidlohr Bueso
2023-06-13 18:12 ` Dave Jiang
2023-06-12 18:10 ` [PATCH 3/7] cxl/mbox: Add sanitation handling machinery Davidlohr Bueso
2023-06-13 16:07 ` Jonathan Cameron
2023-06-13 16:28 ` Davidlohr Bueso
2023-06-14 8:36 ` Jonathan Cameron
2023-06-25 22:13 ` Dan Williams [this message]
2023-06-26 18:17 ` Davidlohr Bueso
2023-06-25 22:18 ` Dan Williams
2023-06-12 18:10 ` [PATCH 4/7] cxl/mem: Wire up Sanitation support Davidlohr Bueso
2023-06-25 22:34 ` Dan Williams
2023-06-12 18:10 ` [PATCH 5/7] cxl/test: Add Sanitize opcode support Davidlohr Bueso
2023-06-12 18:10 ` [PATCH 6/7] cxl/mem: Support Secure Erase Davidlohr Bueso
2023-06-12 18:10 ` [PATCH 7/7] cxl/test: Add Secure Erase opcode support Davidlohr Bueso
2023-06-13 15:26 ` [PATCH v6 0/7] cxl: Support device sanitation Jonathan Cameron
2023-06-13 15:51 ` Jonathan Cameron
2023-06-13 16:25 ` Davidlohr Bueso
2023-06-25 22:44 ` Dan Williams
2023-06-26 21:32 ` Davidlohr Bueso
2023-06-26 22:47 ` Dan Williams
2023-06-27 8:02 ` [PATCH] cxl/pci: Use correct flag for sanitize polling Davidlohr Bueso
2023-06-27 23:01 ` Dan Williams
-- strict thread matches above, loose matches on Subject: below --
2023-04-21 9:23 [PATCH v4 0/7] cxl: Background cmds and device sanitation Davidlohr Bueso
2023-04-21 9:23 ` [PATCH 3/7] cxl/mbox: Add sanitation handling machinery Davidlohr Bueso
2023-04-28 16:43 ` Dave Jiang
2023-04-28 16:46 ` Davidlohr Bueso
2023-04-28 17:37 ` Dave Jiang
2023-05-11 14:45 ` Jonathan Cameron
2023-05-11 16:48 ` Davidlohr Bueso
2023-05-12 17:02 ` Jonathan Cameron
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=6498bbfb35c6f_2ed72947a@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.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