Re: [patch 9/9] Make use of the Master Timer

On Thursday 01 February 2007 15:29, Jiri Bohac wrote:

> If I do:
> 	rdtscll(a)
> 	...
> 	rdtscll(b)
> is it guaranteed that (b > a) ?

It's not architecturally -- unless you have a barrier.

On P4 the micro architecture guarantees it, but there the barrier in
get_cycles_sync is  patched away. On other x86-64s it is generally needed.

The effect can be also seen between CPUs.

> Because of the __vxtime.cpu[cpu].tsc_invalid flag. We may be

You can still precompute it for the HPET etc. case.
They are already slow, but saving a condition there might be still
worth it.

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

---

• References:
  • [patch 0/9] x86_64: reliable TSC-based gettimeofday
    • From: [email protected]
  • Re: [patch 9/9] Make use of the Master Timer
    • From: Andi Kleen <[email protected]>
  • Re: [patch 9/9] Make use of the Master Timer
    • From: Jiri Bohac <[email protected]>

• Prev by Date: Re: [patch 9/9] Make use of the Master Timer
• Next by Date: Re: [BUG] Unable to handle kernel NULL pointer dereference...as_move_to_dispatch+0x11/0x135
• Previous by thread: Re: [patch 9/9] Make use of the Master Timer
• Next by thread: [patch 5/9] Add all the necessary structures to the vsyscall page
• 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]