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
32 lines
1.4 KiB
Plaintext
32 lines
1.4 KiB
Plaintext
# See docs/trace-events.txt for syntax documentation.
|
|
|
|
# hw/input/ps2.c
|
|
ps2_put_keycode(void *opaque, int keycode) "%p keycode %d"
|
|
ps2_read_data(void *opaque) "%p"
|
|
ps2_set_ledstate(void *s, int ledstate) "%p ledstate %d"
|
|
ps2_reset_keyboard(void *s) "%p"
|
|
ps2_write_keyboard(void *opaque, int val) "%p val %d"
|
|
ps2_keyboard_set_translation(void *opaque, int mode) "%p mode %d"
|
|
ps2_mouse_send_packet(void *s, int dx1, int dy1, int dz1, int b) "%p x %d y %d z %d bs %#x"
|
|
ps2_mouse_event_disabled(void *opaque, int dx, int dy, int dz, int buttons_state, int mouse_dx, int mouse_dy, int mouse_dz) "%p x %d y %d z %d bs %#x mx %d my %d mz %d "
|
|
ps2_mouse_event(void *opaque, int dx, int dy, int dz, int buttons_state, int mouse_dx, int mouse_dy, int mouse_dz) "%p x %d y %d z %d bs %#x mx %d my %d mz %d "
|
|
ps2_mouse_fake_event(void *opaque) "%p"
|
|
ps2_write_mouse(void *opaque, int val) "%p val %d"
|
|
ps2_kbd_reset(void *opaque) "%p"
|
|
ps2_mouse_reset(void *opaque) "%p"
|
|
ps2_kbd_init(void *s) "%p"
|
|
ps2_mouse_init(void *s) "%p"
|
|
|
|
# hw/input/milkymist-softusb.c
|
|
milkymist_softusb_memory_read(uint32_t addr, uint32_t value) "addr %08x value %08x"
|
|
milkymist_softusb_memory_write(uint32_t addr, uint32_t value) "addr %08x value %08x"
|
|
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"
|