On Tue, Jun 21, 2022, Kechen Lu wrote: > For debug and test purposes, there are needs to explicitly make > instruction triggered exits could be trapped to userspace. Simply > add a new flag for guest_debug interface could achieve this. > > This patch also fills the userspace accessible field > vcpu->run->hw.hardware_exit_reason for userspace to determine the > original triggered VM-exits. This patch belongs in a different series, AFAICT there are no dependencies between this and allowing per-vCPU disabling of exits. Allowing userspace to exit on "every" instruction exit is going to be much more controversial, largely because it will be difficult for KVM to provide a consistent, robust ABI. E.g. should KVM exit to userspace if an intercepted instruction is encountered by the emualtor? TL;DR: drop this patch from the next version.
