Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier

Andi Kleen wrote:
> Ok. I think it's better to just fix sched_clock() again than to
> add another one.  I can probably
> eliminate the ktime_get() and use something based on jiffies. That will
> be inaccurate for the instable case of course.
>
> I will do that later today.

sched_clock seems a bit weird to use.  In the pv_ops world, it only
counts unstolen time, and it is therefore inherently per-cpu.  The
timestamps should be at least system-wide monotonic.

    J
-
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] i386 tsc: remove xtime_lock'ing around cpufreq notifier
    • From: Andi Kleen <[email protected]>

• References:
  • [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
    • From: Daniel Walker <[email protected]>
  • Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: If not readdir() then what?
• Next by Date: Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
• Previous by thread: Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
• Next by thread: Re: [PATCH] i386 tsc: remove xtime_lock'ing around cpufreq notifier
• 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]