Lines Matching refs:values
96 * Note, kvm_caps fields should *never* have default values, all fields must be
219 } values[KVM_MAX_NR_USER_RETURN_MSRS];
370 struct kvm_user_return_msr_values *values;
384 values = &msrs->values[slot];
385 if (values->host != values->curr) {
386 wrmsrl(kvm_uret_msrs_list[slot], values->host);
387 values->curr = values->host;
440 msrs->values[i].host = value;
441 msrs->values[i].curr = value;
451 value = (value & mask) | (msrs->values[slot].host & ~mask);
452 if (value == msrs->values[slot].curr)
458 msrs->values[slot].curr = value;
2698 * These values are tracked in kvm->arch.cur_xxx variables.
2753 * to this 'correction' to make it sync up with values that only
3007 * system_timestamp/tsc_timestamp values simultaneously: use a master
3008 * copy of host monotonic time values. Update that master copy
3287 /* With all the info we got, fill in the values */
3343 * Fall back to using their values at slightly different moments by
3377 * These values must be snapshotted within the seqcount loop.
3520 * values are architecturally undefined. But, some Linux
3534 * AMD-based CPUs allow non-zero values, but if and only if
9232 changes registers values during IO operation */
9554 * doesn't see old kvmclock values while running with
9562 * so the guest will not see stale values.
9840 * Make sure the user can only configure tsc_khz values that