[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1401111624170.20677@be1.lrz>
Date: Sat, 11 Jan 2014 16:35:00 +0000 (UTC)
From: 7eggert@....de
To: Prarit Bhargava <prarit@...hat.com>
cc: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Len Brown <lenb@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Linn Crosetto <linn@...com>, Pekka Enberg <penberg@...nel.org>,
Yinghai Lu <yinghai@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Toshi Kani <toshi.kani@...com>,
Tang Chen <tangchen@...fujitsu.com>,
Wen Congyang <wency@...fujitsu.com>,
Vivek Goyal <vgoyal@...hat.com>, kosaki.motohiro@...il.com,
dyoung@...hat.com, linux-acpi@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 2/2] x86, e820 disable ACPI Memory Hotplug if memory
mapping is specified by user [v2]
On Fri, 10 Jan 2014, Prarit Bhargava wrote:
> kdump uses memmap=exactmap and mem=X values to configure the memory
> mapping for the kdump kernel. If memory is hotadded during the boot of
> the kdump kernel it is possible that the page tables for the new memory
> cause the kdump kernel to run out of memory.
>
> Since the user has specified a specific mapping ACPI Memory Hotplug should be
> disabled in this case.
I'll ask just in case: Is it possible to want memory hotplug in spite of
using memmap=exactmap or mem=X?
--
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