Emilio G. Cota cb764d0665 qsp: track BQL callers explicitly ... The BQL is acquired via qemu_mutex_lock_iothread(), which makes the profiler assign the associated wait time (i.e. most of BQL wait time) entirely to that function. This loses the original call site information, which does not help diagnose BQL contention. Fix it by tracking the callers explicitly. Signed-off-by: Emilio G. Cota <cota@braap.org> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2018-08-23 18:46:25 +02:00
..
arch-query-cpu-def.c
arch-query-cpu-model-baseline.c
arch-query-cpu-model-comparison.c
arch-query-cpu-model-expansion.c
bdrv-next-monitor-owned.c
blk-commit-all.c
blockdev-close-all-bdrv-states.c
change-state-handler.c
clock-warp.c
cpu-get-clock.c
cpu-get-icount.c
dump.c
error-printf.c	tests: don't silence error reporting for all tests	2018-07-24 17:35:23 +01:00
fd-register.c
fdset.c	monitor: add lock to protect mon_fdsets	2018-06-18 15:48:22 +02:00
gdbstub.c
get-vm-name.c
iothread-lock.c	qsp: track BQL callers explicitly	2018-08-23 18:46:25 +02:00
iothread.c
is-daemonized.c
linux-aio.c	linux-aio: properly bubble up errors from initialization	2018-06-27 13:06:34 +01:00
machine-init-done.c
Makefile.objs	pc-dimm: factor out MemoryDevice interface	2018-05-07 10:00:02 -03:00
migr-blocker.c
monitor.c	monitor: Fix unsafe sharing of @cur_mon among threads	2018-07-23 14:00:03 +02:00
notify-event.c
pc_madt_cpu_entry.c
pci-host-piix.c
qmp_memory_device.c	pc-dimm: factor out MemoryDevice interface	2018-05-07 10:00:02 -03:00
qtest.c
ram-block.c
replay.c
runstate-check.c
set-fd-handler.c
slirp.c
sysbus.c
target-get-monitor-def.c
target-monitor-defs.c
tpm.c
trace-control.c
uuid.c
vm-stop.c
vmgenid.c
vmstate.c
xen-common.c
xen-hvm.c