Revision cd461c8445392d02c268d79f7ed68387b440c4b3 authored by lyx634449800 on 08 April 2024, 02:00:03 UTC, committed by Michael Tokarev on 09 April 2024, 17:42:59 UTC
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 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> Acked-by: Jason Wang <jasowang@redhat.com> Message-Id: <20240408020003.1979-1-yuxue.liu@jaguarmicro.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> (cherry picked from commit 6ae72f609a21cfc56bf655cd4bcded5d07691ce7) Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
1 parent b57b102
File | Mode | Size |
---|---|---|
9p-iov-marshal.c | -rw-r--r-- | 10.1 KB |
9p-iov-marshal.h | -rw-r--r-- | 768 bytes |
9p-marshal.c | -rw-r--r-- | 872 bytes |
9p-marshal.h | -rw-r--r-- | 1.6 KB |
file-op-9p.h | -rw-r--r-- | 5.1 KB |
meson.build | -rw-r--r-- | 730 bytes |
p9array.h | -rw-r--r-- | 5.4 KB |
qemu-fsdev-dummy.c | -rw-r--r-- | 372 bytes |
qemu-fsdev-opts.c | -rw-r--r-- | 2.6 KB |
qemu-fsdev-throttle.c | -rw-r--r-- | 4.6 KB |
qemu-fsdev-throttle.h | -rw-r--r-- | 965 bytes |
qemu-fsdev.c | -rw-r--r-- | 5.0 KB |
qemu-fsdev.h | -rw-r--r-- | 492 bytes |
virtfs-proxy-helper.c | -rw-r--r-- | 31.4 KB |
Computing file changes ...