Re: Using sched_clock for mmio-trace

[email protected] (Frank Ch. Eigler) writes:
> 
> We in systemtap land have the same problem, and so far made do with
> slightly postprocessed per-cpu TSC values.

90+% likely you're not solving your problem correctly this way.

-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: Using sched_clock for mmio-trace
    • From: "Frank Ch. Eigler" <[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)

• Prev by Date: Re: Using sched_clock for mmio-trace
• Next by Date: misleading comment in __oom_kill_task()?
• 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]