RFC virtio fix up started checks
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | virtio: distinguish between started and runninghw/ hw/ hw/ +3 more | +16 | 0 replies | |
| 2/3 | gpio: use virtio_device_runninghw/ | +2 | 0 replies | |
| 3/3 | virtio: revert changes to virtio_device_startedinclude/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 0/3] virtio fix up started checks
This is an attempt to fix up device started checks. Unfortunately this causes failures in CI and I could not figure it out.
The simplest way to test is to set QEMU_CI to 2
on gitlab, then push there.
Alternatively, push to gitlab, then
create pipeline while setting QEMU_CI to 1, then run amd64-fedora-container and then clang-system - that slows things down enough to make the failures trigger.
See: https://gitlab.com/mstredhat/qemu/-/jobs/3279537476
Alex, Viresh, need your help here. Thanks!
Alex, pls note that same failures are triggered by your RFC - if we know the root cause we can discuss solutions. So if you prefer pls go ahead and debug that. Thanks!
Michael S. Tsirkin (3):
virtio: distinguish between started and running
gpio: use virtio_device_running
virtio: revert changes to virtio_device_started
include/hw/virtio/virtio.h | 7 ++++++- hw/virtio/vhost-user-fs.c | 2 +- hw/virtio/vhost-user-gpio.c | 4 ++-- hw/virtio/vhost-user-i2c.c | 4 ++-- hw/virtio/vhost-user-rng.c | 4 ++-- hw/virtio/vhost-user-vsock.c | 2 +- hw/virtio/vhost-vsock.c | 2 +- 7 files changed, 15 insertions(+), 10 deletions(-)
Signature · 1 line
MST