Re: [PATCH] target/riscv: Wake on VS-level external interrupts

2022-06-05 Thread Alistair Francis
On Wed, Jun 1, 2022 at 7:07 AM Andrew Bresticker wrote: > > Whether or not VSEIP is pending isn't reflected in env->mip and must > instead be determined from hstatus.vgein and hgeip. As a result a > CPU in WFI won't wake on a VSEIP, which violates the WFI behavior as > specified in the privileged

Re: [PATCH] target/riscv: Wake on VS-level external interrupts

2022-06-05 Thread Alistair Francis
On Wed, Jun 1, 2022 at 7:07 AM Andrew Bresticker wrote: > > Whether or not VSEIP is pending isn't reflected in env->mip and must > instead be determined from hstatus.vgein and hgeip. As a result a > CPU in WFI won't wake on a VSEIP, which violates the WFI behavior as > specified in the privileged

[PATCH] target/riscv: Wake on VS-level external interrupts

2022-05-31 Thread Andrew Bresticker
Whether or not VSEIP is pending isn't reflected in env->mip and must instead be determined from hstatus.vgein and hgeip. As a result a CPU in WFI won't wake on a VSEIP, which violates the WFI behavior as specified in the privileged ISA. Just use riscv_cpu_all_pending() instead, which already accoun