public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eli Cohen <elic@nvidia.com>
Cc: jasowang@redhat.com, virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] vdpa/mlx5: Support creating resources with uid == 0
Date: Mon, 31 May 2021 18:17:12 -0400	[thread overview]
Message-ID: <20210531181704-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20210531160404.31368-1-elic@nvidia.com>

On Mon, May 31, 2021 at 07:04:04PM +0300, Eli Cohen wrote:
> Currently all resources must be created with uid != 0 which is essential
> when userspace processes are allocating virtquueue resources. Since this
> is a kernel implementation, it is perfectly legal to open resources with
> uid == 0.
> 
> In case firmware supports, avoid allocating user context.
> 
> Signed-off-by: Eli Cohen <elic@nvidia.com>
> ---
> v0 --> v1:
>   Fix typo and modify phrasing

threading's broken now

>  drivers/vdpa/mlx5/core/resources.c | 6 ++++++
>  include/linux/mlx5/mlx5_ifc.h      | 4 +++-
>  2 files changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/vdpa/mlx5/core/resources.c b/drivers/vdpa/mlx5/core/resources.c
> index 6521cbd0f5c2..836ab9ef0fa6 100644
> --- a/drivers/vdpa/mlx5/core/resources.c
> +++ b/drivers/vdpa/mlx5/core/resources.c
> @@ -54,6 +54,9 @@ static int create_uctx(struct mlx5_vdpa_dev *mvdev, u16 *uid)
>  	void *in;
>  	int err;
>  
> +	if (MLX5_CAP_GEN(mvdev->mdev, umem_uid_0))
> +		return 0;
> +
>  	/* 0 means not supported */
>  	if (!MLX5_CAP_GEN(mvdev->mdev, log_max_uctx))
>  		return -EOPNOTSUPP;
> @@ -79,6 +82,9 @@ static void destroy_uctx(struct mlx5_vdpa_dev *mvdev, u32 uid)
>  	u32 out[MLX5_ST_SZ_DW(destroy_uctx_out)] = {};
>  	u32 in[MLX5_ST_SZ_DW(destroy_uctx_in)] = {};
>  
> +	if (!uid)
> +		return;
> +
>  	MLX5_SET(destroy_uctx_in, in, opcode, MLX5_CMD_OP_DESTROY_UCTX);
>  	MLX5_SET(destroy_uctx_in, in, uid, uid);
>  
> diff --git a/include/linux/mlx5/mlx5_ifc.h b/include/linux/mlx5/mlx5_ifc.h
> index 9c68b2da14c6..606d2aeacad4 100644
> --- a/include/linux/mlx5/mlx5_ifc.h
> +++ b/include/linux/mlx5/mlx5_ifc.h
> @@ -1487,7 +1487,9 @@ struct mlx5_ifc_cmd_hca_cap_bits {
>  	u8         uar_4k[0x1];
>  	u8         reserved_at_241[0x9];
>  	u8         uar_sz[0x6];
> -	u8         reserved_at_250[0x8];
> +	u8         reserved_at_248[0x2];
> +	u8         umem_uid_0[0x1];
> +	u8         reserved_at_250[0x5];
>  	u8         log_pg_sz[0x8];
>  
>  	u8         bf[0x1];
> -- 
> 2.31.1


  reply	other threads:[~2021-05-31 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 16:04 [PATCH v1 1/2] vdpa/mlx5: Support creating resources with uid == 0 Eli Cohen
2021-05-31 22:17 ` Michael S. Tsirkin [this message]
2021-06-01  4:35   ` Eli Cohen
2021-06-01  1:54 ` Jason Wang

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=20210531181704-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=elic@nvidia.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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