From: Stefano Garzarella <sgarzare@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: elic@nvidia.com, mst@redhat.com,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH linux-next v6 1/8] vdpa: Introduce and use vdpa device get, set config helpers
Date: Tue, 26 Oct 2021 14:58:17 +0200 [thread overview]
Message-ID: <20211026125817.cr7vld2623hth2wd@steredhat> (raw)
In-Reply-To: <20211026040243.79005-2-parav@nvidia.com>
On Tue, Oct 26, 2021 at 07:02:36AM +0300, Parav Pandit via Virtualization wrote:
>Subsequent patches enable get and set configuration either
>via management device or via vdpa device' config ops.
>
>This requires synchronization between multiple callers to get and set
>config callbacks. Features setting also influence the layout of the
>configuration fields endianness.
>
>To avoid exposing synchronization primitives to callers, introduce
>helper for setting the configuration and use it.
>
>Signed-off-by: Parav Pandit <parav@nvidia.com>
>Reviewed-by: Eli Cohen <elic@nvidia.com>
>Acked-by: Jason Wang <jasowang@redhat.com>
>---
>changelog:
>v4->v5:
> - use vdpa_set_config() API in virtio_vdpa driver
>---
> drivers/vdpa/vdpa.c | 36 ++++++++++++++++++++++++++++++++++++
> drivers/vhost/vdpa.c | 3 +--
> drivers/virtio/virtio_vdpa.c | 3 +--
> include/linux/vdpa.h | 19 ++++---------------
> 4 files changed, 42 insertions(+), 19 deletions(-)
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-10-26 12:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 4:02 [PATCH linux-next v6 0/8] vdpa: enable user to set mac, mtu Parav Pandit via Virtualization
2021-10-26 4:02 ` [PATCH linux-next v6 1/8] vdpa: Introduce and use vdpa device get, set config helpers Parav Pandit via Virtualization
2021-10-26 12:58 ` Stefano Garzarella [this message]
2021-10-26 4:02 ` [PATCH linux-next v6 2/8] vdpa: Introduce query of device config layout Parav Pandit via Virtualization
2021-10-26 4:02 ` [PATCH linux-next v6 3/8] vdpa: Use kernel coding style for structure comments Parav Pandit via Virtualization
2021-10-26 12:58 ` Stefano Garzarella
2021-10-26 4:02 ` [PATCH linux-next v6 4/8] vdpa: Enable user to set mac and mtu of vdpa device Parav Pandit via Virtualization
2021-10-26 13:01 ` Stefano Garzarella
2021-10-26 13:03 ` Parav Pandit via Virtualization
2021-10-26 13:08 ` Michael S. Tsirkin
2021-10-26 13:11 ` Parav Pandit via Virtualization
2021-10-26 13:17 ` Stefano Garzarella
2021-10-26 4:02 ` [PATCH linux-next v6 5/8] vdpa_sim_net: Enable user to set mac address and mtu Parav Pandit via Virtualization
2021-10-26 4:09 ` Jason Wang
2021-10-26 13:12 ` Stefano Garzarella
2021-10-26 4:02 ` [PATCH linux-next v6 6/8] vdpa/mlx5: Fix clearing of VIRTIO_NET_F_MAC feature bit Parav Pandit via Virtualization
2021-10-26 4:09 ` Jason Wang
2021-10-26 4:02 ` [PATCH linux-next v6 7/8] vdpa/mlx5: Support configuration of MAC Parav Pandit via Virtualization
2021-10-26 4:02 ` [PATCH linux-next v6 8/8] vdpa/mlx5: Forward only packets with allowed MAC address Parav Pandit via Virtualization
2021-10-26 4:13 ` 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=20211026125817.cr7vld2623hth2wd@steredhat \
--to=sgarzare@redhat.com \
--cc=elic@nvidia.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--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