Re: PMTMR running too fast

On Tue, 2006-12-05 at 11:34 -0800, john stultz wrote:
> 
> > Should tsc be preferred to pit though?
> 
> Depends on your system. If C2/C3 or cpufreq state changes are
> detected, we mark the tsc as unstable.  

Turns out I was seeing C2 states. I'll stick with PIT for now.

Thanks,
Ian.

-- 
Ian Campbell

If ignorance is bliss, why aren't there more happy people?

Attachment: signature.asc
Description: This is a digitally signed message part

---

• References:
  • PMTMR running too fast
    • From: Ian Campbell <[email protected]>
  • Re: PMTMR running too fast
    • From: john stultz <[email protected]>
  • Re: PMTMR running too fast
    • From: Ian Campbell <[email protected]>
  • Re: PMTMR running too fast
    • From: john stultz <[email protected]>
  • Re: PMTMR running too fast
    • From: Ian Campbell <[email protected]>
  • Re: PMTMR running too fast
    • From: john stultz <[email protected]>

• Prev by Date: Re: [PATCH] WorkStruct: Implement generic UP cmpxchg() where an arch doesn't support it
• Next by Date: ... and more...
• Previous by thread: Re: PMTMR running too fast
• Next by thread: Re: PMTMR running too fast
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]