From: Vivek Goyal <vgoyal@redhat.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
Prarit Bhargava <prarit@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <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>,
Tang Chen <tangchen@cn.fujitsu.com>,
Wen Congyang <wency@cn.fujitsu.com>,
Dave Young <dyoung@redhat.com>,
linux-acpi@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] x86, acpi memory hotplug, add parameter to disable memory hotplug
Date: Tue, 14 Jan 2014 09:36:18 -0500 [thread overview]
Message-ID: <20140114143618.GA3096@redhat.com> (raw)
In-Reply-To: <1389663689.1792.268.camel@misato.fc.hp.com>
On Mon, Jan 13, 2014 at 06:41:29PM -0700, Toshi Kani wrote:
> On Tue, 2014-01-14 at 10:11 +0900, Yasuaki Ishimatsu wrote:
> :
> > >> I think we need a knob manually enable mem-hotplug when specify memmap. But
> > >> it is another story.
> > >>
> > >> Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> > >
> > > As mentioned, self-NAK. I have seen a system that I needed to specify
> > > memmap=exactmap & had hotplug memory. I will only keep the acpi_no_memhotplug
> > > option in the next version of the patch.
> >
> >
> > Your following first patch is simply and makes sense.
> >
> > http://marc.info/?l=linux-acpi&m=138922019607796&w=2
> >
>
> In this option, it also requires changing kexec-tools to specify the new
> option for kdump. It won't be simpler.
I am thinking that instead of modifying kexec-tools, it can be made
part of the documentation so that user is expected to pass this parameter.
In fedora, we can modify /etc/sysconfig/kdump and add the parameter by
default so that user's don't have to worry about passing it.
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>
next prev parent reply other threads:[~2014-01-14 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 21:56 Prarit Bhargava
2014-01-13 22:17 ` KOSAKI Motohiro
2014-01-13 23:41 ` Prarit Bhargava
2014-01-14 1:11 ` Yasuaki Ishimatsu
2014-01-14 1:41 ` Toshi Kani
2014-01-14 2:43 ` Yasuaki Ishimatsu
2014-01-14 10:58 ` Prarit Bhargava
2014-01-14 15:17 ` Toshi Kani
2014-01-14 11:05 ` Prarit Bhargava
2014-01-14 14:37 ` Vivek Goyal
2014-01-14 15:26 ` Vivek Goyal
2014-01-14 15:31 ` Toshi Kani
2014-01-14 14:36 ` Vivek Goyal [this message]
2014-01-14 1:45 ` Dave Young
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=20140114143618.GA3096@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox