Ingo Molnar wrote:
> just in case someone sees false positives and wants to turn it off.
Why not make 0=off?
J
-
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/
- Follow-Ups:
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Ravikiran G Thirumalai <kiran@scalex86.org>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- References:
- [patch] Change softlockup trigger limit using a kernel parameter
- From: Ravikiran G Thirumalai <kiran@scalex86.org>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Andrew Morton <akpm@linux-foundation.org>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Ravikiran G Thirumalai <kiran@scalex86.org>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Andrew Morton <akpm@linux-foundation.org>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Ingo Molnar <mingo@elte.hu>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Ravikiran G Thirumalai <kiran@scalex86.org>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Ingo Molnar <mingo@elte.hu>
- [patch] Change softlockup trigger limit using a kernel parameter
- Prev by Date: [PATCH] fix modpost warnings for xtensa
- Next by Date: Re: [1/2] 2.6.22-git: known regressions
- Previous by thread: Re: [patch] Change softlockup trigger limit using a kernel parameter
- Next by thread: Re: [patch] Change softlockup trigger limit using a kernel parameter
- Index(es):
 |