Re: [PATCH] target/riscv: fix satp_mode_finalize() when satp_mode.supported = 0

2023-08-22 Thread Alistair Francis
On Thu, Aug 17, 2023 at 11:29 AM Daniel Henrique Barboza wrote: > > In the same emulated RISC-V host, the 'host' KVM CPU takes 4 times > longer to boot than the 'rv64' KVM CPU. > > The reason is an unintended behavior of riscv_cpu_satp_mode_finalize() > when satp_mode.supported = 0, i.e. when cpu_

Re: [PATCH] target/riscv: fix satp_mode_finalize() when satp_mode.supported = 0

2023-08-22 Thread Andrew Jones
On Thu, Aug 17, 2023 at 12:29:03PM -0300, Daniel Henrique Barboza wrote: > In the same emulated RISC-V host, the 'host' KVM CPU takes 4 times > longer to boot than the 'rv64' KVM CPU. > > The reason is an unintended behavior of riscv_cpu_satp_mode_finalize() > when satp_mode.supported = 0, i.e. wh

[PATCH] target/riscv: fix satp_mode_finalize() when satp_mode.supported = 0

2023-08-17 Thread Daniel Henrique Barboza
In the same emulated RISC-V host, the 'host' KVM CPU takes 4 times longer to boot than the 'rv64' KVM CPU. The reason is an unintended behavior of riscv_cpu_satp_mode_finalize() when satp_mode.supported = 0, i.e. when cpu_init() does not set satp_mode_max_supported(). satp_mode_max_from_map(map) d