qemu-riscv
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 04/22] target/riscv: Improve fidelity of guest external in


From: Alistair Francis
Subject: Re: [PATCH v2 04/22] target/riscv: Improve fidelity of guest external interrupts
Date: Thu, 9 Sep 2021 16:44:25 +1000

On Thu, Sep 2, 2021 at 9:26 PM Anup Patel <anup.patel@wdc.com> wrote:
>
> The guest external interrupts for external interrupt controller are
> not delivered to the guest running under hypervisor on time. This
> results in a guest having sluggish response to serial console input
> and other I/O events. To improve timely delivery of guest external
> interrupts, we check and inject interrupt upon every sret instruction.
>
> Signed-off-by: Anup Patel <anup.patel@wdc.com>
> ---
>  target/riscv/op_helper.c | 9 +++++++++
>  1 file changed, 9 insertions(+)
>
> diff --git a/target/riscv/op_helper.c b/target/riscv/op_helper.c
> index ee7c24efe7..4c995c239e 100644
> --- a/target/riscv/op_helper.c
> +++ b/target/riscv/op_helper.c
> @@ -129,6 +129,15 @@ target_ulong helper_sret(CPURISCVState *env, 
> target_ulong cpu_pc_deb)
>
>      riscv_cpu_set_mode(env, prev_priv);
>
> +    /*
> +     * QEMU does not promptly deliver guest external interrupts
> +     * to a guest running on a hypervisor which in-turn is running
> +     * on QEMU. We make dummy call to riscv_cpu_update_mip() upon
> +     * every sret instruction so that QEMU pickup guest external
> +     * interrupts sooner.
> +     */
> +     riscv_cpu_update_mip(env_archcpu(env), 0, 0);

This doesn't seem right. I don't understand why we need this?

riscv_cpu_update_mip() is called when an interrupt is delivered to the
CPU, if we are missing interrupts then that is a bug somewhere else.

Alistair



reply via email to

[Prev in Thread] Current Thread [Next in Thread]