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
fd-register.c
fdset.c
gdbstub.c
get-vm-name.c
iothread-lock.c
iothread.c
is-daemonized.c
linux-aio.c
machine-init-done.c
Makefile.objs
migr-blocker.c
monitor.c
notify-event.c
pc_madt_cpu_entry.c
pci-host-piix.c
qmp_memory_device.c
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