Re: [PATCH 1/2] hvf: avoid repeatedly setting trap debug for each cpu

2025-04-14 Thread Alex Bennée
Mads Ynddal writes: > From: Mads Ynddal > > hvf_arch_set_traps is already called from a context of a specific > CPUState, so we don't need to do a nested CPU_FOREACH. > > It also results in an error from hv_vcpu_set_sys_reg, as it may only be > called from the thread owning the vCPU. > > Tested-

Re: [PATCH 1/2] hvf: avoid repeatedly setting trap debug for each cpu

2025-04-02 Thread Daniel Gomez
On Wed, Apr 02, 2025 at 03:52:28PM +0100, Mads Ynddal wrote: > From: Mads Ynddal > > hvf_arch_set_traps is already called from a context of a specific > CPUState, so we don't need to do a nested CPU_FOREACH. > > It also results in an error from hv_vcpu_set_sys_reg, as it may only be > called fro