[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191108121030.5466dd3e.cohuck@redhat.com>
Date: Fri, 8 Nov 2019 12:10:30 +0100
From: Cornelia Huck <cohuck@...hat.com>
To: Parav Pandit <parav@...lanox.com>
Cc: alex.williamson@...hat.com, davem@...emloft.net,
kvm@...r.kernel.org, netdev@...r.kernel.org, saeedm@...lanox.com,
kwankhede@...dia.com, leon@...nel.org, jiri@...lanox.com,
linux-rdma@...r.kernel.org
Subject: Re: [PATCH net-next 07/19] vfio/mdev: Introduce sha1 based mdev
alias
On Thu, 7 Nov 2019 10:08:22 -0600
Parav Pandit <parav@...lanox.com> wrote:
> Some vendor drivers want an identifier for an mdev device that is
> shorter than the UUID, due to length restrictions in the consumers of
> that identifier.
>
> Add a callback that allows a vendor driver to request an alias of a
> specified length to be generated for an mdev device. If generated,
> that alias is checked for collisions.
>
> It is an optional attribute.
> mdev alias is generated using sha1 from the mdev name.
>
> Reviewed-by: Saeed Mahameed <saeedm@...lanox.com>
> Signed-off-by: Parav Pandit <parav@...lanox.com>
> ---
> drivers/vfio/mdev/mdev_core.c | 123 ++++++++++++++++++++++++++++++-
> drivers/vfio/mdev/mdev_private.h | 5 +-
> drivers/vfio/mdev/mdev_sysfs.c | 13 ++--
> include/linux/mdev.h | 4 +
> 4 files changed, 135 insertions(+), 10 deletions(-)
Is this (or any of the other mdev alias patches) different from what I
reviewed in the past?
Powered by blists - more mailing lists