Ingo Molnar wrote:
> sched_clock(), as its name suggests it, is meant for the scheduler's
> use. The scheduler generally only needs to measure time when the CPU is
> busy - not across idle periods. So sched_clock() can (and will) break
> across certain types of ACPI idle methods.
>
Hm, or more specifically, why would that be a problem for softlockup?
Do you mean it doesn't measure time during ACPI idle? That would just
make it trigger later than it would otherwise.
Andrew is reporting that it is triggering very early, and making the
machine feel jerky. How can that be related to sched_clock's quality,
unless its too broken to be useful to anyone for anything?
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/
[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]
