>
> The present situation is inconsistent: "notsc" removes cpuinfo's
> "tsc" flag in the UP case (when cpu_data[0] is boot_cpu_data), but
> not in the SMP case. I don't believe HPA's recent mods affected that
> behaviour, but it is made consistent (cleared in SMP case too) by the
> patch I sent
On Thu, 7 Dec 2000, Christopher Friesen wrote:
> Kotsovinos Vangelis wrote:
> >
> > Is there any way to measure (with microsecond accuracy) the time of a
> > program execution (without using Machine Specific Registers) ?
> > I've already tried getrusage(), times() and clock() but they all have
Ok, I'll check it out...
Thank you very much,
--) Vangelis
On Thu, 7 Dec 2000, Karim Yaghmour wrote:
>
> You might want to try the Linux Trace Toolkit. It'll give you microsecond
> accuracy on program execution time measurement.
>
> Check it out:
> http://www.opersys.com/LTT
>
> Karim
>
You might want to try the Linux Trace Toolkit. It'll give you microsecond
accuracy on program execution time measurement.
Check it out:
http://www.opersys.com/LTT
Karim
Kotsovinos Vangelis wrote:
>
> Is there any way to measure (with microsecond accuracy) the time of a
> program execution (wi
On Thu, 7 Dec 2000, Hugh Dickins wrote:
> The present situation is inconsistent: "notsc" removes cpuinfo's
> "tsc" flag in the UP case (when cpu_data[0] is boot_cpu_data), but
> not in the SMP case. I don't believe HPA's recent mods affected that
> behaviour, but it is made consistent (cleared i
On Thu, 7 Dec 2000, Maciej W. Rozycki wrote:
> On 7 Dec 2000, H. Peter Anvin wrote:
>
> > Unfortunately the most important instance of the in-kernel flag -- the
> > global one in the somewhat misnamed boot_cpu_data.x86_features --
> > isn't actually readable in the /proc/cpuinfo file. It is per
Kotsovinos Vangelis wrote:
>
> Is there any way to measure (with microsecond accuracy) the time of a
> program execution (without using Machine Specific Registers) ?
> I've already tried getrusage(), times() and clock() but they all have
> 10 millisecond accuracy, even though they claim to have m
On 7 Dec 2000, H. Peter Anvin wrote:
> Unfortunately the most important instance of the in-kernel flag -- the
> global one in the somewhat misnamed boot_cpu_data.x86_features --
> isn't actually readable in the /proc/cpuinfo file. It is perfectly
> possible (e.g. the "notsc" option) for ALL the
Followup to: <[EMAIL PROTECTED]>
By author:Tigran Aivazian <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> while we are on this subject, please let me emphasize that you should
> _not_ be using cpuid instruction to detect the presence of TSC but should
> parse the /proc/cpuinfo file.
On Thu, 7 Dec 2000, Tigran Aivazian wrote:
> Hi,
>
> How about TSC? I know this has disadvantages such as:
>
> a) not all machines have TSC
while we are on this subject, please let me emphasize that you should
_not_ be using cpuid instruction to detect the presence of TSC but should
parse the
Hi,
How about TSC? I know this has disadvantages such as:
a) not all machines have TSC
b) not all machines that claim to have TSC have a usable one.
c) on SMP the kernel makes a best effort to synchronize TSC but this may
or may not be guaranteed
d) you still need a userspace implementation t
11 matches
Mail list logo
