58f88d0bf7
The replay subsystem does not provide any way to see what's going on and how the replay events interleave with other things happening in QEMU. Add trace events to improve debuggability; to avoid having too many events reimplement all functions in terms of (non-traced) replay_getc and replay_putc and add a single trace event for each datum that is extracted or written. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
12 lines
557 B
Text
12 lines
557 B
Text
replay_put_byte(uint8_t event) "%02x"
|
|
replay_put_event(uint8_t event) "%02x"
|
|
replay_put_word(uint16_t event) "%04x"
|
|
replay_put_dword(uint32_t event) "%08x"
|
|
replay_put_qword(uint64_t event) "%016" PRIx64
|
|
replay_get_byte(uint8_t byte) "%02x"
|
|
replay_get_word(uint16_t word) "%04x"
|
|
replay_get_dword(uint32_t dword) "%08x"
|
|
replay_get_qword(uint64_t qword) "%016" PRIx64
|
|
replay_fetch_data_kind(void) ""
|
|
replay_get_event(uint32_t current, uint8_t data) "#%u data=%02x"
|
|
replay_advance_current_icount(uint64_t current_icount, int diff) "current=%" PRIu64 " diff=%d"
|