Messages in this thread | | | Date | Thu, 19 Jul 2007 16:50:58 +0200 | From | Ingo Molnar <> | Subject | Re: [patch] fix the softlockup watchdog to actually work |
| |
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> 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.
no, the return value after idling can be completely random on some boxes, on a 64-bit scale - triggering the softlockup watchdog randomly. (some boxes return random TSC values, etc.) Again, it's fine for the scheduler's purpose, that's why i named it sched_clock().
the proper clocksource use within the kernel is ktime_get() [or ktime_get_ts()]. Do not abuse sched_clock() for such things.
Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |