linux-kernel - Re: [patch-rt 4/4] sched: mark SCHED

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 29 Jan 2009 10:58:28 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...e.hu>,
	Carsten Emde <carsten.emde@...dl.org>
Subject: Re: [patch-rt 4/4] sched: mark SCHED_HRTICK broken

On Wed, 2009-01-28 at 21:29 +0000, Thomas Gleixner wrote:
> plain text document attachment
> (do-not-configure-sched-hrtick-since-it-is-currently-broken.patch)
> SCHED_HRTICK is broken and not yet fixed in mainline. WTF is it still
> enabled in -rt ?

It got fixed in mainline, but past .26. That said, we still disabled in
in mainline because of performance issues.

> Suggested-by: Peter Zijlstra <peterz@...radead.org>
> Tested-by: Carsten Emde <C.Emde@...dl.org>
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
> ---
>  kernel/Kconfig.hz |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: linux-2.6.26/kernel/Kconfig.hz
> ===================================================================
> --- linux-2.6.26.orig/kernel/Kconfig.hz
> +++ linux-2.6.26/kernel/Kconfig.hz
> @@ -55,4 +55,4 @@ config HZ
>  	default 1000 if HZ_1000
>  
>  config SCHED_HRTICK
> -	def_bool HIGH_RES_TIMERS && X86
> +	def_bool HIGH_RES_TIMERS && X86 && BROKEN
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/