In user emulation, threads -- implemented as CPU -- are
created/destroyed, but never reset. There is no point in
allowing the user emulation access the sysemu/reset API.
Philippe Mathieu-Daudé (5):
target/i386: Restrict qapi/qapi-events-run-state.h to system emulation
target/i386: Restrict sysemu/reset.h to system emulation
target/loongarch: Restrict sysemu/reset.h to system emulation
target/s390x: Restrict sysemu/reset.h to system emulation
hw/core: Only build CPU reset handlers with system emulation