aboutsummaryrefslogtreecommitdiff
path: root/hw/input/trace-events
diff options
context:
space:
mode:
authorGerd Hoffmann <kraxel@redhat.com>2016-06-23 11:51:35 +0200
committerGerd Hoffmann <kraxel@redhat.com>2016-07-12 09:25:28 +0200
commitc80276b4206d534daaaf87305df5805db1b8db02 (patch)
treefa8fc8e0b65d1cc219fc975a18152614a8e4f0a3 /hw/input/trace-events
parentd7b7f526b18dacda8ee559dc18c13d4430a78b68 (diff)
downloadqemu-c80276b4206d534daaaf87305df5805db1b8db02.zip
qemu-c80276b4206d534daaaf87305df5805db1b8db02.tar.gz
qemu-c80276b4206d534daaaf87305df5805db1b8db02.tar.bz2
input: add trace events for full queues
It isn't unusual to happen, for example during reboot when the guest doesn't reveice events for a while. So better don't flood stderr with alarming messages. Turn them into tracepoints instead so they can be enabled in case they are needed for trouble-shooting. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> Message-id: 1466675495-28797-1-git-send-email-kraxel@redhat.com
Diffstat (limited to 'hw/input/trace-events')
-rw-r--r--hw/input/trace-events6
1 files changed, 6 insertions, 0 deletions
diff --git a/hw/input/trace-events b/hw/input/trace-events
index 00fcec1..f24dff2 100644
--- a/hw/input/trace-events
+++ b/hw/input/trace-events
@@ -23,3 +23,9 @@ milkymist_softusb_memory_write(uint32_t addr, uint32_t value) "addr %08x value %
milkymist_softusb_mevt(uint8_t m) "m %d"
milkymist_softusb_kevt(uint8_t m) "m %d"
milkymist_softusb_pulse_irq(void) "Pulse IRQ"
+
+# hw/input/hid.c
+hid_kbd_queue_full(void) "queue full"
+
+# hw/input/virtio
+virtio_input_queue_full(void) "queue full"