|| ||Andi Kleen <andi-AT-firstfloor.org> |
|| ||Venkatesh Pallipadi <venki-AT-google.com> |
|| ||Re: [PATCH] x86: Export tsc related information in sysfs |
|| ||Sat, 15 May 2010 11:57:04 +0200|
|| ||Ingo Molnar <mingo-AT-elte.hu>, Thomas Gleixner <tglx-AT-linutronix.de>,
"H. Peter Anvin" <hpa-AT-zytor.com>,
Chris Mason <chris.mason-AT-oracle.com>,
Dan Magenheimer <dan.magenheimer-AT-oracle.com>|
|| ||Article, Thread
Venkatesh Pallipadi <firstname.lastname@example.org> writes:
> From: Dan Magenheimer <email@example.com>
> Kernel information about calibrated value of tsc_khz and
> tsc_stability (result of tsc warp test) are useful bits of information
> for any app that wants to use TSC directly. Export this read_only
> information in sysfs.
Is this really a good idea? It will encourage the applications
to use RDTSC directly, but there are all kinds of constraints on
that. Even the kernel has a hard time with them, how likely
is it that applications will get all that right?
It would be better to fix them to use the vsyscalls instead.
Or if they can't use the vsyscalls for some reason today fix them.
This way if anything changes again in TSC the kernel could
shield the applications.
firstname.lastname@example.org -- Speaking for myself only.
to post comments)