Searched refs:diag318 (Results 1 – 4 of 4) sorted by relevance
157 run->s.regs.diag318 = get_diag318_info(); in test_set_and_verify_various_reg_values()170 TEST_ASSERT(run->s.regs.diag318 == get_diag318_info(), in test_set_and_verify_various_reg_values()172 run->s.regs.diag318); in test_set_and_verify_various_reg_values()192 run->s.regs.diag318 = 0x4B1D; in test_clear_kvm_dirty_regs_bits()199 TEST_ASSERT(run->s.regs.diag318 != 0x4B1D, in test_clear_kvm_dirty_regs_bits()201 run->s.regs.diag318); in test_clear_kvm_dirty_regs_bits()
600 __u64 diag318; /* diagnose 0x318 info */ member
5148 vcpu->arch.diag318_info.val = kvm_run->s.regs.diag318; in sync_regs_fmt2()5246 kvm_run->s.regs.diag318 = vcpu->arch.diag318_info.val; in store_regs_fmt2()