Re: [PATCH v3 00/24] cpus: Restrict CPU has_work() handlers to system emulation

2025-03-09 Thread Philippe Mathieu-Daudé
On 25/1/25 18:01, Philippe Mathieu-Daudé wrote: Philippe Mathieu-Daudé (24): cpus: Restrict cpu_has_work() to system emulation cpus: Un-inline cpu_has_work() cpus: Introduce SysemuCPUOps::has_work() handler target/alpha: Move has_work() from CPUClass to SysemuCPUOps target/arm: Mo

Re: [PATCH v3 00/24] cpus: Restrict CPU has_work() handlers to system emulation

2025-02-10 Thread Philippe Mathieu-Daudé
On 25/1/25 18:01, Philippe Mathieu-Daudé wrote: Philippe Mathieu-Daudé (24): cpus: Restrict cpu_has_work() to system emulation cpus: Un-inline cpu_has_work() cpus: Introduce SysemuCPUOps::has_work() handler target/alpha: Move has_work() from CPUClass to SysemuCPUOps target/arm: Mo

[PATCH v3 00/24] cpus: Restrict CPU has_work() handlers to system emulation

2025-01-25 Thread Philippe Mathieu-Daudé
Missing review: 16 (I plan to merge this myself once reviewed) Since v2: - Check mandatory SysemuCPUOps handlers in class_post_init() v1 cover: On user emulation, threads always have work to do, and CPUClass::has_work() is never called. Restrict it to system emulation, allowing to simplify a bi