Searched refs:diag318 (Results 1 – 7 of 7) sorted by relevance
159 run->s.regs.diag318 = get_diag318_info(); in test_set_and_verify_various_reg_values()172 TEST_ASSERT(run->s.regs.diag318 == get_diag318_info(), in test_set_and_verify_various_reg_values()174 run->s.regs.diag318); in test_set_and_verify_various_reg_values()194 run->s.regs.diag318 = 0x4B1D; in test_clear_kvm_dirty_regs_bits()201 TEST_ASSERT(run->s.regs.diag318 != 0x4B1D, in test_clear_kvm_dirty_regs_bits()203 run->s.regs.diag318); in test_clear_kvm_dirty_regs_bits()
270 __u64 diag318; /* diagnose 0x318 info */ member
286 __u64 diag318; /* diagnose 0x318 info */ member
599 __u64 diag318; /* diagnose 0x318 info */ member
594 cs->kvm_run->s.regs.diag318 = env->diag318_info; in kvm_arch_put_registers()700 env->diag318_info = cs->kvm_run->s.regs.diag318; in kvm_arch_get_registers()1551 cs->kvm_run->s.regs.diag318 = diag318_info; in kvm_s390_set_diag318()
132 DEF_FEAT(DIAG_318, "diag318", SCLP_FAC134, 0, "Control program name and version codes")
4887 vcpu->arch.diag318_info.val = kvm_run->s.regs.diag318; in sync_regs_fmt2()4996 kvm_run->s.regs.diag318 = vcpu->arch.diag318_info.val; in store_regs_fmt2()