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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 26 Dec 2008 15:22:36 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	paulmck@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, akpm@...ux-foundation.org, ralf@...ux-mips.org,
	kernel@...tstofly.org, hskinnemoen@...el.com, cooloney@...nel.org,
	tony.luck@...el.com, geert@...ux-m68k.org, zippel@...ux-m68k.org,
	jwboyer@...ux.vnet.ibm.com, mporter@...nel.crashing.org,
	grant.likely@...retlab.ca, paulus@...ba.org,
	benh@...nel.crashing.org, dhowells@...hat.com,
	yasutake.koichi@...panasonic.com, lethal@...ux-sh.org,
	hpa@...or.com
Subject: Re: [PATCH -tip] Switch arm defconfig files from
	CONFIG_CLASSIC_RCU to CONFIG_TREE_RCU.


* Sam Ravnborg <sam@...nborg.org> wrote:

> On Thu, Dec 25, 2008 at 09:36:11AM +0100, Ingo Molnar wrote:
> > 
> > below is the fix for another small buglet that hits architectures that do 
> > not include kernel/Kconfig.preempt.
> 
> What is needed to let all architectures include Kconfig.preempt?
> We should not advertise preemption if not supported,
> but we could do this by a simple Kconfig symbol:
> 
> config HAVE_PREEMPT
> 	bool
> 
> And let all architectures that supports preemption do:
> 
> config "ARCH"
> 	select HAVE_PREEMPT
> 
> But maybe there is a simpler solution

Since a preemptive kernel is not supported by all architectures, there has 
to be per arch ways to express this - i.e. i think your solution is the 
cleanest.

	Ingo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ