Andrew Morton wrote:
> blktrace. I've seen a couple of trace/debug-style things which use
> sched_clock for timestamping event collection. I think lttng does exotic
> things with TSCs, performing private skew correction, although that might
> have changed now.
>
I'm not worried about things using the tsc directly. But since we hook
into sched_clock, anyone using it is going to get the pv_ops backend's
behaviour, which is targeted at making the scheduler work properly
rather than all these secondary uses.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- From: Daniel Walker <[email protected]>
- Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- From: Andi Kleen <[email protected]>
- Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- From: Andrew Morton <[email protected]>
- Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- From: Andi Kleen <[email protected]>
- Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- From: Andrew Morton <[email protected]>
- Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- From: Andrew Morton <[email protected]>
- [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- Prev by Date: Re: [PATCH 3/17] afs: convert afs_dir_get_page to read_kmap_page
- Next by Date: Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- Previous by thread: Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- Next by thread: Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
- Index(es):
 |