linux-kernel - Re: [PATCH] memory hotplug disable boot option

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: <20100625152819.GC13421@basil.fritz.box>
Date:	Fri, 25 Jun 2010 17:28:19 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Nathan Fontenot <nfont@...tin.ibm.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] memory hotplug disable boot option

> Yes, this would work to reduce the number of memory sections created.  The reason

Note it could be done on the sysfs interface level too, e.g. have one
entry that gets a bitmap as input/output.

> I have not gone this route is that increasing the memory section size would
> break DLPAR memory add and remove for powerpc pseries.

How would it break it?

But aren't you breaking this anyways by disabling the sysfs entries?!?

-Andi


-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/