linux-kernel - Re: Patches for REALLY TINY 386 kernels

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070718184734.GE3898@one.firstfloor.org>
Date:	Wed, 18 Jul 2007 20:47:34 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Andi Kleen <andi@...stfloor.org>, "H. Peter Anvin" <hpa@...or.com>,
	Jonathan Campbell <jon@...dgrounds.com>,
	linux-kernel@...r.kernel.org, torvalds@...nsmeta.com
Subject: Re: Patches for REALLY TINY 386 kernels

> And the hypothetical case where RAM is hotplugged and/or recognized after the
> kernel has been loaded by the bootloader? I do not claim to be an expert, but

RAM hotadd needs working user space to trigger it.

Besides it typically comes with cpuhotplug too, so you couldn't even
discard __cpuinit.

-Andi (who is out of the thread because it's getting silly) 
-
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/