Andrew Morton wrote:
> It's weird. And I don't think the locking selftest code calls
> sched_clock() (or any other time-related thing) at all, does it?
>
I guess it ends up going through the scheduler, which does use it.
But... <shrug>
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/
- References:
- Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- From: Andrew Morton <[email protected]>
- Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- From: Andrew Morton <[email protected]>
- Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- From: Andrew Morton <[email protected]>
- Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- From: Andrew Morton <[email protected]>
- Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- Prev by Date: [PATCH 3/3] MMC: OMAP: Clean up omap set_ios and make MMC_POWER_ON work
- Next by Date: RE: suspend2 merge (was Re: [Suspend2-devel] Re: CFS and suspend2: hang in atomic copy)
- Previous by thread: Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- Next by thread: Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- Index(es):
 |