5d75648b56
Having to include qapi-events.h just for QAPIEvent is suboptimal, but quite tolerable now. It'll become problematic when we have events conditional on the target, because then qapi-events.h won't be usable from target-independent code anymore. Avoid that by generating it into separate files. Signed-off-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com> Message-Id: <20190214152251.2073-6-armbru@redhat.com> |
||
---|---|---|
.. | ||
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 | ||
ramfb.c | ||
replay.c | ||
runstate-check.c | ||
set-fd-handler.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 |