Re: [patch 00/22] high resolution timers / dynamic ticks - V3

> But usually the problem wasn't that it was too slow, but that
> it completely stopped in C2 or deeper. I don't think there
> is a way to work around that except for not using C2 or deeper
> (not an option) or using a different timer source.

actually it's supposed to be C3 where lapic stops, not C2.

For systems with C3, lapic is not usable for timers as is, and hpet or
similar needs to be used instead.


-
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/

---

• Follow-Ups:
  • Re: [patch 00/22] high resolution timers / dynamic ticks - V3
    • From: Andi Kleen <[email protected]>

• References:
  • [patch 00/22] high resolution timers / dynamic ticks - V3
    • From: Thomas Gleixner <[email protected]>
  • Re: [patch 00/22] high resolution timers / dynamic ticks - V3
    • From: Andrew Morton <[email protected]>
  • Re: [patch 00/22] high resolution timers / dynamic ticks - V3
    • From: Ingo Molnar <[email protected]>
  • Re: [patch 00/22] high resolution timers / dynamic ticks - V3
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: how to get the kernel to be more "verbose"?
• Next by Date: Re: [-mm PATCH] fixed PCMCIA au1000_generic.c
• Previous by thread: Re: [patch 00/22] high resolution timers / dynamic ticks - V3
• Next by thread: Re: [patch 00/22] high resolution timers / dynamic ticks - V3
• 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]