Jeremy Fitzhardinge wrote:
Zachary Amsden wrote:
Jeremy Fitzhardinge wrote:
Zachary Amsden wrote:
Scheduled (or available) time and real time are good notions. Stolen
time is debatable. But TSC is basically just always wrong. That's
why I don't want to overload the rdtsc op
Zachary Amsden wrote:
> Jeremy Fitzhardinge wrote:
>> Zachary Amsden wrote:
>>
>>> Scheduled (or available) time and real time are good notions. Stolen
>>> time is debatable. But TSC is basically just always wrong. That's
>>> why I don't want to overload the rdtsc operation.
>> Well, in t
Jeremy Fitzhardinge wrote:
Zachary Amsden wrote:
Scheduled (or available) time and real time are good notions. Stolen
time is debatable. But TSC is basically just always wrong. That's
why I don't want to overload the rdtsc operation.
Well, in the Xen case it is actually guaranteed t
Zachary Amsden wrote:
> Scheduled (or available) time and real time are good notions. Stolen
> time is debatable. But TSC is basically just always wrong. That's
> why I don't want to overload the rdtsc operation.
Well, in the Xen case it is actually guaranteed to be correct and useful
as real t
Andi Kleen wrote:
.write_msr = native_write_msr,
.read_tsc = native_read_tsc,
.read_pmc = native_read_pmc,
+ .get_scheduled_cycles = native_read_tsc,
+ .get_cpu_khz = native_calculate_cpu_khz,
.load_tr_desc = native_load_tr_desc,
Description missin
> .write_msr = native_write_msr,
> .read_tsc = native_read_tsc,
> .read_pmc = native_read_pmc,
> + .get_scheduled_cycles = native_read_tsc,
> + .get_cpu_khz = native_calculate_cpu_khz,
> .load_tr_desc = native_load_tr_desc,
Description missing?
Please write at lea
Zachary Amsden wrote:
#include "mach_timer.h"
@@ -102,9 +103,6 @@ unsigned long long sched_clock(void)
{
unsigned long long this_offset;
- if (unlikely(custom_sched_clock))
- return (*custom_sched_clock)();
-
/*
* Fall back to jiffies if there's no
7 matches
Mail list logo
