Re: [PATCH 06/16] cpus: Improve cpu_exit() docstring

[Paolo Bonzini <pbonzini@redhat.com>]

On 8/13/26 20:16, Philippe Mathieu-Daudé wrote:
> Mention that what the vCPU exits is the execution loop :)
> Mention some of the reasons for calling cpu_exit().
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd@oss.qualcomm.com>
> ---
>   include/hw/core/cpu.h | 7 ++++---
>   1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/include/hw/core/cpu.h b/include/hw/core/cpu.h
> index f1ac492714e..7da81f3ee85 100644
> --- a/include/hw/core/cpu.h
> +++ b/include/hw/core/cpu.h
> @@ -1037,10 +1037,11 @@ static inline void cpu_set_pc(CPUState *cpu, vaddr addr)
>   void cpu_reset_interrupt(CPUState *cpu, int mask);
>   
>   /**
> - * cpu_exit:
> - * @cpu: The CPU to exit.
> + * cpu_exit - Request the CPU to exit its execution loop
> + * @cpu: The CPU to interrupt.
>    *
> - * Requests the CPU @cpu to exit execution.
> + * Request an immediate exit from the CPU execution loop to process
> + * pending work such as interrupts, timers, or other async requests.

More precise: to sleep or process asynchronous work items (see the 
run_on_cpu() family of functions).

Paolo