Johan,
I think on mobile systems like notebooks there are influences from
‘speed-step’ technologies that will give you very unreliable results
in using RDTSC. On these systems the clock rate seems to vary over
time.
| Norbert Kawulski | mailto:xxxxx@stollmann.de |
| Stollmann T.P.GmbH, Development | http://www.stollmann.de |
–If it’s ISDN or Bluetooth, make sure it’s driven by Stollmann–
“I’m not as innocent as I look”
Could you expand on that a bit?
// Johan
> -----Original Message-----
> From: Avi Shmidman [mailto:xxxxx@excalibur.co.il]
> Sent: den 27 juni 2001 11:24
> To: NT Developers Interest List
> Subject: [ntdev] Re: Clock resolution on a PC and WinNT
>
>
>
> >* You’ll have to synchronize the counter value… to the
> system time exactly
>
> Is it possible to use the StallFactor from the Processor
> Control Region to
> get a more accurate value? (This is what the KM
> KeStallExecutionProcessor
> routine uses to achieve microsecond precision).
>
> - Avi
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@esrange.ssc.se
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
You are currently subscribed to ntdev as: xxxxx@stollmann.de
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com