Re: Performance overhead of get_cycles_sync

Ingo Molnar <[email protected]> writes:

> the TSC clocksource (and hence the vsyscall code) is turned off on 
> systems that fail the TOD/CLOCK portion of this test:

Which is not on core2 which was the question about. And if it was
turned off it wouldn't use get_cycles_sync() at all.

-Andi
--
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: Performance overhead of get_cycles_sync
    • From: Ingo Molnar <[email protected]>

• References:
  • Performance overhead of get_cycles_sync
    • From: Dor Laor <[email protected]>
  • Re: Performance overhead of get_cycles_sync
    • From: Ingo Molnar <[email protected]>
  • Re: Performance overhead of get_cycles_sync
    • From: Ingo Molnar <[email protected]>
  • Re: Performance overhead of get_cycles_sync
    • From: Arjan van de Ven <[email protected]>
  • Re: Performance overhead of get_cycles_sync
    • From: Ingo Molnar <[email protected]>

• Prev by Date: Re: [PATCH] xen: relax signature check
• Next by Date: Re: 2.6.22.14 oops msg with commvault galaxy ?
• Previous by thread: Re: Performance overhead of get_cycles_sync
• Next by thread: Re: Performance overhead of get_cycles_sync
• 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]