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 sys
On 12/20/22 06:56, Philippe Mathieu-Daudé wrote:
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-sta
On Tue, 2022-12-20 at 15:56 +0100, Philippe Mathieu-Daudé wrote:
> 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
