Re: [Fwd: sched_clock() has poor resolution]

Hi,

On Thu, Sep 22, 2005 at 09:28:49AM +0200, Pierre Ossman wrote:
>  * Let sched_clock() follow the time source. Don't have it coupled to
> the TSC.
> 
>  * Init the TSC even though it isn't used for anything but sched_clock().

As pmtmr requires somewhat working TSCs, you can even use TSC if pmtmr is
used as a time source:

static int init_pmtmr(char* override)
...
        /* we use the TSC for delay_pmtmr, so make sure it exists */
        if (!cpu_has_tsc)
                return -ENODEV;
...

So at least for this case, sched_clock() can and should use TSC, not
jiffies, AFAICS.

Thanks,
	Dominik
-
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:
  • [Fwd: sched_clock() has poor resolution]
    • From: Pierre Ossman <[email protected]>

• Prev by Date: Re: [uml-devel] [PATCH 06/10] uml: run mconsole "sysrq" in process context
• Next by Date: Re: Linus GIT tree disappeared from http://www.kernel.org/git/?
• Previous by thread: [Fwd: sched_clock() has poor resolution]
• Next by thread: [PATCH 1/3] Bogus tls from gdt
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]