path: root/trace-events
diff options
authorStefan Hajnoczi <stefanha@linux.vnet.ibm.com>2011-09-13 13:34:37 +0100
committerBlue Swirl <blauwirbel@gmail.com>2011-09-17 15:14:24 +0000
commit4e1837f855b88fdced2941b17509e13b0c8fa518 (patch)
tree55a661085c835405fed67c2d2731b62417d8addf /trace-events
parent689d7e2fadb27d696528eb1f86eb3e3e19e07761 (diff)
trace: add virtio_set_status() trace event
The virtio device lifecycle can be observed by looking at the sequence of set status operations. This is especially important for catching the reset operation (status value 0), which resets the device and all virtqueues. Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
Diffstat (limited to 'trace-events')
1 files changed, 1 insertions, 0 deletions
diff --git a/trace-events b/trace-events
index 84b5a88fd..829dc927c 100644
--- a/trace-events
+++ b/trace-events
@@ -42,6 +42,7 @@ virtqueue_pop(void *vq, void *elem, unsigned int in_num, unsigned int out_num) "
virtio_queue_notify(void *vdev, int n, void *vq) "vdev %p n %d vq %p"
virtio_irq(void *vq) "vq %p"
virtio_notify(void *vdev, void *vq) "vdev %p vq %p"
+virtio_set_status(void *vdev, uint8_t val) "vdev %p val %u"
# hw/virtio-serial-bus.c
virtio_serial_send_control_event(unsigned int port, uint16_t event, uint16_t value) "port %u, event %u, value %u"