Lines Matching full:tsc

8854  * list, the value saved is not subject to the TSC offset that is
8863 		report_skip("%s : \"Use TSC offsetting\" exec control not supported", __func__);  in vmx_store_tsc_test()
9129  * the TSC changes due to a TSC increment (where X is
9134  * The guest code above reads the starting TSC after VM-entry. At this
9136  * the guest code reads the current TSC in a loop, storing the value
9143  * must be delivered before the next instruction retires. Hence, a TSC
9145  * cannot be stored. If a TSC value past the deadline *is* stored,
9181 	       "Last stored guest TSC (%lu) < TSC deadline (%lu)",  in vmx_preemption_timer_expiry_test()
10323  * Set 'use TSC offsetting' and set the guest offset to the
10324  * inverse of the host's current TSC value, so that the guest starts running
10325  * with an effective TSC value of 0.
10343  * This function only considers the "use TSC offsetting" VM-execution
10344  * control.  It does not handle "use TSC scaling" (because the latter
10377 		test_skip("CPU doesn't support the 'use TSC offsetting' processor-based VM-execution control.\n");  in rdtsc_vmexit_diff_test()
10387 	 * to the TSC multiplier and TSC offset fields in the VMCS12,  in rdtsc_vmexit_diff_test()
10501 	 * available with the "TSC flag" and used to populate the MSR lists.  in atomic_switch_msrs_test()