Re: [PULL 19/89] target/riscv: Fix itrigger when icount is used

2023-05-10 Thread Michael Tokarev
08.05.2023 01:22, Alistair Francis wrote: On Fri, May 5, 2023 at 11:04 AM Alistair Francis wrote: From: LIU Zhiwei When I boot a ubuntu image, QEMU output a "Bad icount read" message and exit. The reason is that when execute helper_mret or helper_sret, it will cause a call to icount_get_raw_

Re: [PULL 19/89] target/riscv: Fix itrigger when icount is used

2023-05-07 Thread Alistair Francis
On Fri, May 5, 2023 at 11:04 AM Alistair Francis wrote: > > From: LIU Zhiwei > > When I boot a ubuntu image, QEMU output a "Bad icount read" message and exit. > The reason is that when execute helper_mret or helper_sret, it will > cause a call to icount_get_raw_locked (), which needs set can_do_i

[PULL 19/89] target/riscv: Fix itrigger when icount is used

2023-05-04 Thread Alistair Francis
From: LIU Zhiwei When I boot a ubuntu image, QEMU output a "Bad icount read" message and exit. The reason is that when execute helper_mret or helper_sret, it will cause a call to icount_get_raw_locked (), which needs set can_do_io flag on cpustate. Thus we setting this flag when execute these tw