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 hw/core/meson.build | 2 +- target/i386/cpu.c | 2 +- target/i386/helper.c | 2 +- target/loongarch/cpu.c | 2 ++ target/s390x/cpu.c | 4 +++- 5 files changed, 8 insertions(+), 4 deletions(-) -- 2.38.1
