From: Prarit Bhargava <prarit@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Dave Young <dyoung@redhat.com>,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH] acpi memory hotplug, add parameter to disable memory hotplug for kexec
Date: Thu, 09 Jan 2014 20:04:49 -0500 [thread overview]
Message-ID: <52CF4731.6090106@redhat.com> (raw)
In-Reply-To: <20140109214425.GD12111@redhat.com>
On 01/09/2014 04:44 PM, Vivek Goyal wrote:
> On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
>> On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal <vgoyal@redhat.com> wrote:
>>> On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
>
> Makes sense. Something like "acpi_no_memhotplug" or "acpi_disable_memhotplug"
> or something else.
>
FWIW ... after thinking about it and some of the other debug I've had to do,
maybe acpi=no_memhotplug and acpi=no_cpuhotplug are in order here. I've had to
disable both during hardware enablement debug and it seems that it "fits" the
current acpi disabling scheme.
Unless, of course, Rafael still objects.
P.
next prev parent reply other threads:[~2014-01-10 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1389220181-14474-1-git-send-email-prarit@redhat.com>
[not found] ` <3476878.EqQiEtA2Ag@vostro.rjw.lan>
2014-01-09 15:00 ` [PATCH] acpi memory hotplug, add parameter to disable memory hotplug for kexec Vivek Goyal
2014-01-09 21:34 ` KOSAKI Motohiro
2014-01-09 21:44 ` Vivek Goyal
2014-01-10 1:04 ` Prarit Bhargava [this message]
2014-01-10 1:35 ` Rafael J. Wysocki
2014-01-10 3:57 ` Yasuaki Ishimatsu
2014-01-10 11:01 ` Prarit Bhargava
2014-01-10 1:31 ` Rafael J. Wysocki
2014-01-10 14:38 ` Vivek Goyal
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=52CF4731.6090106@redhat.com \
--to=prarit@redhat.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=kosaki.motohiro@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vgoyal@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).