Re: [PATCH 08/27] target/riscv: store RISCVCPUDef struct directly in the class

On 4/24/25 11:04 AM, Philippe Mathieu-Daudé wrote: On 24/4/25 15:52, Daniel Henrique Barboza wrote: Hi, This patch breaks RISC-V KVM build in my env. The issues are down there: On 4/6/25 4:02 AM, Paolo Bonzini wrote: Prepare for adding more fields to RISCVCPUDef and reading them in riscv_c

Re: [PATCH 08/27] target/riscv: store RISCVCPUDef struct directly in the class

On 24/4/25 15:52, Daniel Henrique Barboza wrote: Hi, This patch breaks RISC-V KVM build in my env. The issues are down there: On 4/6/25 4:02 AM, Paolo Bonzini wrote: Prepare for adding more fields to RISCVCPUDef and reading them in riscv_cpu_init: instead of storing the misa_mxl_max field in R

Re: [PATCH 08/27] target/riscv: store RISCVCPUDef struct directly in the class

Hi, This patch breaks RISC-V KVM build in my env. The issues are down there: On 4/6/25 4:02 AM, Paolo Bonzini wrote: Prepare for adding more fields to RISCVCPUDef and reading them in riscv_cpu_init: instead of storing the misa_mxl_max field in RISCVCPUClass, ensure that there's always a valid R

[PATCH 08/27] target/riscv: store RISCVCPUDef struct directly in the class

Prepare for adding more fields to RISCVCPUDef and reading them in riscv_cpu_init: instead of storing the misa_mxl_max field in RISCVCPUClass, ensure that there's always a valid RISCVCPUDef struct and go through it. Reviewed-by: Alistair Francis Signed-off-by: Paolo Bonzini --- target/riscv/cpu.