[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140110211204.GC19115@redhat.com>
Date: Fri, 10 Jan 2014 16:12:04 -0500
From: Vivek Goyal <vgoyal@...hat.com>
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>, 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, Jan 10, 2014 at 02:04:58PM -0500, Prarit Bhargava wrote:
> kdump uses memmap=exactmap and mem=X values
Minor nit. Kdump only uses memmap=exactmap and not mem=X. mem=X is there
for debugging. So lets fix the changelog.
[..]
> static int __init parse_memmap_opt(char *str)
> {
> + int ret;
> +
> while (str) {
> char *k = strchr(str, ',');
>
> if (k)
> *k++ = 0;
>
> - parse_memmap_one(str);
> + ret = parse_memmap_one(str);
> + if (!ret)
> + set_acpi_no_memhotplug();
We want to call this only in case of memmap=exactmap and not other memmap=
options. So I think instead of here, call it inside parse_memmap_one()
where exactmap check is done.
if (!strncmp(p, "exactmap", 8)) {
set_acpi_no_memhotplug();
}
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/
Powered by blists - more mailing lists