All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Len Brown <lenb@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linn Crosetto <linn@hp.com>, Pekka Enberg <penberg@kernel.org>,
	Yinghai Lu <yinghai@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Toshi Kani <toshi.kani@hp.com>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	kosaki.motohiro@gmail.com, dyoung@redhat.com,
	linux-acpi@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] x86, e820 disable ACPI Memory Hotplug if memory mapping is specified by user [v2]
Date: Fri, 10 Jan 2014 16:12:04 -0500	[thread overview]
Message-ID: <20140110211204.GC19115@redhat.com> (raw)
In-Reply-To: <1389380698-19361-4-git-send-email-prarit@redhat.com>

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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Len Brown <lenb@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linn Crosetto <linn@hp.com>, Pekka Enberg <penberg@kernel.org>,
	Yinghai Lu <yinghai@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Toshi Kani <toshi.kani@hp.com>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	kosaki.motohiro@gmail.com, dyoung@redhat.com,
	linux-acpi@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] x86, e820 disable ACPI Memory Hotplug if memory mapping is specified by user [v2]
Date: Fri, 10 Jan 2014 16:12:04 -0500	[thread overview]
Message-ID: <20140110211204.GC19115@redhat.com> (raw)
In-Reply-To: <1389380698-19361-4-git-send-email-prarit@redhat.com>

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

  reply	other threads:[~2014-01-10 21:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 19:04 [PATCH 0/2] Add option to disable ACPI Memory Hotplug [v2] Prarit Bhargava
2014-01-10 19:04 ` Prarit Bhargava
2014-01-10 19:04 ` [PATCH 0/2] Add option to disable ACPI Memory Hotplug Prarit Bhargava
2014-01-10 19:04 ` [PATCH 1/2] acpi memory hotplug, add parameter to disable memory hotplug [v2] Prarit Bhargava
2014-01-10 19:04   ` Prarit Bhargava
2014-01-10 21:34   ` Toshi Kani
2014-01-10 21:34     ` Toshi Kani
2014-01-10 19:04 ` [PATCH 2/2] x86, e820 disable ACPI Memory Hotplug if memory mapping is specified by user [v2] Prarit Bhargava
2014-01-10 19:04   ` Prarit Bhargava
2014-01-10 21:12   ` Vivek Goyal [this message]
2014-01-10 21:12     ` Vivek Goyal
2014-01-10 21:34   ` Toshi Kani
2014-01-10 21:34     ` Toshi Kani
2014-01-11 16:35   ` 7eggert
2014-01-11 16:35     ` 7eggert
2014-01-12 23:46     ` Prarit Bhargava
2014-01-12 23:46       ` Prarit Bhargava
2014-01-13 20:31       ` KOSAKI Motohiro
2014-01-13 20:31         ` KOSAKI Motohiro
2014-01-13 23:39         ` Prarit Bhargava
2014-01-13 23:39           ` Prarit Bhargava
2014-01-14  0:33           ` Toshi Kani
2014-01-14  0:33             ` Toshi Kani
2014-01-14  0:53             ` H. Peter Anvin
2014-01-14  0:53               ` H. Peter Anvin
2014-01-14  1:09               ` Toshi Kani
2014-01-14  1:09                 ` Toshi Kani
2014-01-14  1:29                 ` H. Peter Anvin
2014-01-14  1:29                   ` H. Peter Anvin
2014-01-14  1:40                   ` Toshi Kani
2014-01-14  1:40                     ` Toshi Kani
2014-01-14  1:52                 ` Dave Young
2014-01-14  1:52                   ` Dave Young
2014-01-14  1:47                   ` Toshi Kani
2014-01-14  1:47                     ` Toshi Kani
2014-01-14 11:02             ` Prarit Bhargava
2014-01-14 11:02               ` Prarit Bhargava

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140110211204.GC19115@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dyoung@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kosaki.motohiro@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linn@hp.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=penberg@kernel.org \
    --cc=prarit@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=toshi.kani@hp.com \
    --cc=wency@cn.fujitsu.com \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.