linux-kernel - Re: [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v2]

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]

Message-ID: <52D009D7.1010600@redhat.com>
Date:	Fri, 10 Jan 2014 09:55:19 -0500
From:	Prarit Bhargava <prarit@...hat.com>
To:	Vivek Goyal <vgoyal@...hat.com>
CC:	linux-kernel@...r.kernel.org, Len Brown <lenb@...nel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>, kosaki.motohiro@...il.com,
	dyoung@...hat.com, linux-acpi@...r.kernel.org,
	kexec@...ts.infradead.org
Subject: Re: [PATCH] acpi memory hotplug, add parameter to disable memory
 hotplug [v2]



On 01/10/2014 09:49 AM, Vivek Goyal wrote:
> On Fri, Jan 10, 2014 at 09:36:55AM -0500, Prarit Bhargava wrote:
> 
> [..]
>> This can also be reproduced by using the memmap=exactmap and mem=X
>> parameters on the main kernel and booting.
>>
>> This patchset resolves the problem by adding a kernel parameter,
>> acpi_no_memhotplug, to disable ACPI memory hotplug.
> 
> Hi Prarit,
> 
> People seem to like the idea of disabling hotplug automatically if
> memmap=exactmap or mem=X is passed on command line. Can you please take
> care of that too. That way we would not have to modify kexec-tools and
> kernel update will fix this issue.

Oh, okay.  I'll do that right now.

P.

> 
> Thanks
> Vivek
--
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/