Re: [PATCH v2] target/riscv: Restrict KVM-specific fields from ArchCPU

On Sun, Jun 25, 2023 at 5:30 AM Philippe Mathieu-Daudé wrote: > > These fields shouldn't be accessed when KVM is not available. > > Restrict the KVM timer migration state. Rename the KVM timer > post_load() handler accordingly, because cpu_post_load() is > too generic. > > Signed-off-by: Philippe

Re: [PATCH v2] target/riscv: Restrict KVM-specific fields from ArchCPU

On 24/6/23 21:29, Philippe Mathieu-Daudé wrote: These fields shouldn't be accessed when KVM is not available. Restrict the KVM timer migration state. Rename the KVM timer post_load() handler accordingly, because cpu_post_load() is too generic. Signed-off-by: Philippe Mathieu-Daudé --- Since v1

Re: [PATCH v2] target/riscv: Restrict KVM-specific fields from ArchCPU

On 6/24/23 16:29, Philippe Mathieu-Daudé wrote: These fields shouldn't be accessed when KVM is not available. Restrict the KVM timer migration state. Rename the KVM timer post_load() handler accordingly, because cpu_post_load() is too generic. Signed-off-by: Philippe Mathieu-Daudé --- Rev

[PATCH v2] target/riscv: Restrict KVM-specific fields from ArchCPU

These fields shouldn't be accessed when KVM is not available. Restrict the KVM timer migration state. Rename the KVM timer post_load() handler accordingly, because cpu_post_load() is too generic. Signed-off-by: Philippe Mathieu-Daudé --- Since v1 https://lore.kernel.org/qemu-devel/2023040516045