From: Dave Jiang <dave.jiang@intel.com>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Anil Keshavamurthy <anil.s.keshavamurthy@intel.com>
Subject: Re: [PATCH v1] dmaengine: idxd: Narrow the restriction on BATCH to ver. 1 only
Date: Wed, 12 Mar 2025 15:18:28 -0700 [thread overview]
Message-ID: <3ccbe50e-e47e-4406-885e-600bd193a23c@intel.com> (raw)
In-Reply-To: <20250312221511.277954-1-vinicius.gomes@intel.com>
On 3/12/25 3:15 PM, Vinicius Costa Gomes wrote:
> Allow BATCH operations to be submitted and the capability to be
> exposed for DSA version 2 (or later) devices.
>
> DSA version 2 devices allow safe submission of BATCH operations.
>
> Signed-off-by: Anil Keshavamurthy <anil.s.keshavamurthy@intel.com>
> Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dma/idxd/cdev.c | 6 ++++--
> drivers/dma/idxd/sysfs.c | 6 ++++--
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/dma/idxd/cdev.c b/drivers/dma/idxd/cdev.c
> index ff94ee892339..6a1dc15ee485 100644
> --- a/drivers/dma/idxd/cdev.c
> +++ b/drivers/dma/idxd/cdev.c
> @@ -439,10 +439,12 @@ static int idxd_submit_user_descriptor(struct idxd_user_context *ctx,
> * DSA devices are capable of indirect ("batch") command submission.
> * On devices where direct user submissions are not safe, we cannot
> * allow this since there is no good way for us to verify these
> - * indirect commands.
> + * indirect commands. Narrow the restriction of operations with the
> + * BATCH opcode to only DSA version 1 devices.
> */
> if (is_dsa_dev(idxd_dev) && descriptor.opcode == DSA_OPCODE_BATCH &&
> - !wq->idxd->user_submission_safe)
> + wq->idxd->hw.version == DEVICE_VERSION_1 &&
> + !wq->idxd->user_submission_safe)
> return -EINVAL;
> /*
> * As per the programming specification, the completion address must be
> diff --git a/drivers/dma/idxd/sysfs.c b/drivers/dma/idxd/sysfs.c
> index 6af493f6ba77..9f0701021af0 100644
> --- a/drivers/dma/idxd/sysfs.c
> +++ b/drivers/dma/idxd/sysfs.c
> @@ -1208,9 +1208,11 @@ static ssize_t op_cap_show_common(struct device *dev, char *buf, unsigned long *
>
> /* On systems where direct user submissions are not safe, we need to clear out
> * the BATCH capability from the capability mask in sysfs since we cannot support
> - * that command on such systems.
> + * that command on such systems. Narrow the restriction of operations with the
> + * BATCH opcode to only DSA version 1 devices.
> */
> - if (i == DSA_OPCODE_BATCH/64 && !confdev_to_idxd(dev)->user_submission_safe)
> + if (i == DSA_OPCODE_BATCH/64 && !confdev_to_idxd(dev)->user_submission_safe &&
> + confdev_to_idxd(dev)->hw.version == DEVICE_VERSION_1)
> clear_bit(DSA_OPCODE_BATCH % 64, &val);
>
> pos += sysfs_emit_at(buf, pos, "%*pb", 64, &val);
next prev parent reply other threads:[~2025-03-12 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 22:15 [PATCH v1] dmaengine: idxd: Narrow the restriction on BATCH to ver. 1 only Vinicius Costa Gomes
2025-03-12 22:18 ` Dave Jiang [this message]
2025-03-14 2:09 ` Yi Sun
2025-04-03 0:57 ` Fenghua Yu
2025-04-03 1:38 ` Vinicius Costa Gomes
2025-04-29 15:01 ` Dave Jiang
2025-05-14 15:03 ` Vinod Koul
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=3ccbe50e-e47e-4406-885e-600bd193a23c@intel.com \
--to=dave.jiang@intel.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.