From: Jason Wang <jasowang@redhat.com>
To: lyx634449800 <yuxue.liu@jaguarmicro.com>
Cc: eperezma@redhat.com, sgarzare@redhat.com, mst@redhat.com,
qemu-stable@nongnu.org, qemu-devel@nongnu.org, kwolf@redhat.com
Subject: Re: [PATCH] vdpa-dev: Fix the issue of device status not updating when configuration interruption is triggered
Date: Sun, 7 Apr 2024 11:45:52 +0800 [thread overview]
Message-ID: <CACGkMEs6FE7iZJAspCacWs+v4XTs9GsTHNdDVtcqoNfdDF_+3Q@mail.gmail.com> (raw)
In-Reply-To: <20240407032240.1898-1-yuxue.liu@jaguarmicro.com>
On Sun, Apr 7, 2024 at 11:22 AM lyx634449800 <yuxue.liu@jaguarmicro.com> wrote:
>
> The set_config callback function vhost_vdpa_device_get_config in
> vdpa-dev does not fetch the current device status from the hardware
> device, causing the GUEST OS to not receive the latest device status
nit: no need for upper case here.
> information.
>
> The hardware updates the config status of the vdpa device and then
> notifies the OS. The GUEST OS receives an interrupt notification,
> triggering a get_config access in the kernel, which then enters qemu
> internally. Ultimately, the vhost_vdpa_device_get_config function of
> vdpa-dev is called
>
> One scenario encountered is when the device needs to bring down the
> vdpa net device. After modifying the status field of virtio_net_config
> in the hardware, it sends an interrupt notification. However, the guest
> OS always receives the STATUS field as VIRTIO_NET_S_LINK_UP.
>
> Signed-off-by: Yuxue Liu <yuxue.liu@jaguarmicro.com>
This aligns with the vhost-net support for vDPA.
Acked-by: Jason Wang <jasowang@redhat.com>
Thanks
> ---
> hw/virtio/vdpa-dev.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/hw/virtio/vdpa-dev.c b/hw/virtio/vdpa-dev.c
> index 13e87f06f6..64b96b226c 100644
> --- a/hw/virtio/vdpa-dev.c
> +++ b/hw/virtio/vdpa-dev.c
> @@ -195,7 +195,14 @@ static void
> vhost_vdpa_device_get_config(VirtIODevice *vdev, uint8_t *config)
> {
> VhostVdpaDevice *s = VHOST_VDPA_DEVICE(vdev);
> + int ret;
>
> + ret = vhost_dev_get_config(&s->dev, s->config, s->config_size,
> + NULL);
> + if (ret < 0) {
> + error_report("get device config space failed");
> + return;
> + }
> memcpy(config, s->config, s->config_size);
> }
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-04-07 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 3:22 [PATCH] vdpa-dev: Fix the issue of device status not updating when configuration interruption is triggered lyx634449800
2024-04-07 3:45 ` Jason Wang [this message]
2024-04-08 2:00 ` [PATCH v2] " lyx634449800
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=CACGkMEs6FE7iZJAspCacWs+v4XTs9GsTHNdDVtcqoNfdDF_+3Q@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=eperezma@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=yuxue.liu@jaguarmicro.com \
/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;
as well as URLs for NNTP newsgroup(s).