From: "Alex Bennée" <alex.bennee@linaro.org>
To: chenh <chenh@yusur.tech>
Cc: raphael.norwitz@nutanix.com, mst@redhat.com, jasowang@redhat.com,
kwolf@redhat.com, hreitz@redhat.com, qemu-block@nongnu.org,
houyl@yusur.tech, zy@yusur.tech, lulu@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2] hw/virtio/vhost-user: support obtain vdpa device's mac address automatically
Date: Wed, 21 Sep 2022 19:23:12 +0100 [thread overview]
Message-ID: <87mtas60x8.fsf@linaro.org> (raw)
In-Reply-To: <20220921060026.392164-1-chenh@yusur.tech>
chenh <chenh@yusur.tech> writes:
> From: Hao Chen <chenh@yusur.tech>
>
> When use dpdk-vdpa tests vdpa device. You need to specify the mac address to
> start the virtual machine through libvirt or qemu, but now, the libvirt or
> qemu can call dpdk vdpa vendor driver's ops .get_config through vhost_net_get_config
> to get the mac address of the vdpa hardware without manual configuration.
>
> v1->v2:
> Only copy ETH_ALEN data of netcfg for some vdpa device such as
> NVIDIA BLUEFIELD DPU(BF2)'s netcfg->status is not right.
> We only need the mac address and don't care about the status field.
>
> Signed-off-by: Hao Chen <chenh@yusur.tech>
> ---
> hw/block/vhost-user-blk.c | 1 -
> hw/net/virtio-net.c | 7 +++++++
> hw/virtio/vhost-user.c | 19 -------------------
> 3 files changed, 7 insertions(+), 20 deletions(-)
>
> diff --git a/hw/block/vhost-user-blk.c b/hw/block/vhost-user-blk.c
> index 9117222456..5dca4eab09 100644
> --- a/hw/block/vhost-user-blk.c
> +++ b/hw/block/vhost-user-blk.c
> @@ -337,7 +337,6 @@ static int vhost_user_blk_connect(DeviceState *dev, Error **errp)
>
> vhost_dev_set_config_notifier(&s->dev, &blk_ops);
>
> - s->vhost_user.supports_config = true;
<snip>
NACK from me. The supports_config flag is there for a reason.
>
> diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
> index bd24741be8..8b01078249 100644
> --- a/hw/virtio/vhost-user.c
> +++ b/hw/virtio/vhost-user.c
> @@ -2013,8 +2013,6 @@ static int vhost_user_backend_init(struct vhost_dev *dev, void *opaque,
> }
>
> if (virtio_has_feature(features, VHOST_USER_F_PROTOCOL_FEATURES)) {
> - bool supports_f_config = vus->supports_config ||
> - (dev->config_ops && dev->config_ops->vhost_dev_config_notifier);
> uint64_t protocol_features;
>
> dev->backend_features |= 1ULL << VHOST_USER_F_PROTOCOL_FEATURES;
> @@ -2033,23 +2031,6 @@ static int vhost_user_backend_init(struct vhost_dev *dev, void *opaque,
> */
> protocol_features &= VHOST_USER_PROTOCOL_FEATURE_MASK;
>
> - if (supports_f_config) {
> - if (!virtio_has_feature(protocol_features,
> - VHOST_USER_PROTOCOL_F_CONFIG)) {
> - error_setg(errp, "vhost-user device expecting "
> - "VHOST_USER_PROTOCOL_F_CONFIG but the vhost-user backend does "
> - "not support it.");
> - return -EPROTO;
> - }
> - } else {
> - if (virtio_has_feature(protocol_features,
> - VHOST_USER_PROTOCOL_F_CONFIG)) {
> - warn_reportf_err(*errp, "vhost-user backend supports "
> - "VHOST_USER_PROTOCOL_F_CONFIG but QEMU does not.");
> - protocol_features &= ~(1ULL << VHOST_USER_PROTOCOL_F_CONFIG);
> - }
> - }
> -
> /* final set of protocol features */
> dev->protocol_features = protocol_features;
> err = vhost_user_set_protocol_features(dev, dev->protocol_features);
--
Alex Bennée
next prev parent reply other threads:[~2022-09-21 18:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 6:00 [PATCH v2] hw/virtio/vhost-user: support obtain vdpa device's mac address automatically chenh
2022-09-21 17:56 ` Raphael Norwitz
2022-09-22 1:34 ` Jason Wang
2022-09-22 9:56 ` Michael S. Tsirkin
2022-09-23 3:21 ` 陈浩
2022-09-23 3:36 ` Jason Wang
2026-02-03 12:48 ` Michael S. Tsirkin
2026-02-04 7:09 ` Cindy Lu
2022-09-23 3:53 ` houyl
2022-09-23 4:05 ` Jason Wang
2022-09-23 6:19 ` Michael S. Tsirkin
2022-09-23 6:20 ` Michael S. Tsirkin
2022-09-21 18:23 ` Alex Bennée [this message]
2022-09-21 19:24 ` Michael S. Tsirkin
2022-09-22 10:02 ` Alex Bennée
2022-09-22 10:19 ` Michael S. Tsirkin
2022-09-23 3:30 ` 陈浩
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=87mtas60x8.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=chenh@yusur.tech \
--cc=houyl@yusur.tech \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=zy@yusur.tech \
/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.