Searched refs:DEBUG_DIRTY (Results 1 - 5 of 5) sorted by relevance

/linux-master/arch/arm64/kvm/hyp/include/hyp/
H A Ddebug-sr.h135 if (!vcpu_get_flag(vcpu, DEBUG_DIRTY))
154 if (!vcpu_get_flag(vcpu, DEBUG_DIRTY))
165 vcpu_clear_flag(vcpu, DEBUG_DIRTY);
H A Dsysreg-sr.h243 if (has_vhe() || vcpu_get_flag(vcpu, DEBUG_DIRTY))
260 if (has_vhe() || vcpu_get_flag(vcpu, DEBUG_DIRTY))
/linux-master/arch/arm64/kvm/
H A Ddebug.c119 * - The guest is not using debug (DEBUG_DIRTY clear).
123 !vcpu_get_flag(vcpu, DEBUG_DIRTY) ||
163 * the guest is not actively using them (see the DEBUG_DIRTY
232 * debug ioctl. The existing DEBUG_DIRTY mechanism ensures
242 vcpu_set_flag(vcpu, DEBUG_DIRTY);
272 vcpu_set_flag(vcpu, DEBUG_DIRTY);
H A Dsys_regs.c610 vcpu_set_flag(vcpu, DEBUG_DIRTY);
623 * All writes will set the DEBUG_DIRTY flag to ensure the hyp code
640 vcpu_set_flag(vcpu, DEBUG_DIRTY);
/linux-master/arch/arm64/include/asm/
H A Dkvm_host.h815 #define DEBUG_DIRTY __vcpu_single_flag(iflags, BIT(4)) macro

Completed in 248 milliseconds