Re: Using sched_clock for mmio-trace

On Sat, 2007-02-17 at 15:56 +0100, Andi Kleen wrote:
> > This is one of the reasons why we don't just use good old
> > do_gettimeofday(), since it takes locks and can lead to lock recursion
> > if parts of itself are probed.
> 
> do_gettimeofday doesn't take locks.
> 
> Only restriction is that you can't single step it with long 
> pauses between instructions.

Err, it uses read side of xtime lock, so you can not call it from a
place which write locks xtime lock.

	tglx


-
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: Using sched_clock for mmio-trace
    • From: Andi Kleen <[email protected]>

• References:
  • Using sched_clock for mmio-trace
    • From: Jeff Muizelaar <[email protected]>
  • Re: Using sched_clock for mmio-trace
    • From: [email protected] (Frank Ch. Eigler)
  • Re: Using sched_clock for mmio-trace
    • From: Andi Kleen <[email protected]>
  • Re: Using sched_clock for mmio-trace
    • From: "Frank Ch. Eigler" <[email protected]>
  • Re: Using sched_clock for mmio-trace
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: 2.6.20-git13 kernel BUG at /mnt/md0/devel/linux-git/kernel/time/tick-sched.c:168
• Next by Date: [mmc] incorrect behavior on resume
• Previous by thread: Re: Using sched_clock for mmio-trace
• Next by thread: Re: Using sched_clock for mmio-trace
• 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]