From: Prarit Bhargava <prarit@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: toshi.kani@hp.com, kexec@lists.infradead.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
isimatu.yasuaki@jp.fujitsu.com, kosaki.motohiro@gmail.com,
dyoung@redhat.com, Vivek Goyal <vgoyal@redhat.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v3]
Date: Wed, 15 Jan 2014 06:21:47 -0500 [thread overview]
Message-ID: <52D66F4B.8080301@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1401141642020.3375@chino.kir.corp.google.com>
On 01/14/2014 07:42 PM, David Rientjes wrote:
> On Tue, 14 Jan 2014, Prarit Bhargava wrote:
>
>> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
>> index b9e9bd8..ea93f75 100644
>> --- a/Documentation/kernel-parameters.txt
>> +++ b/Documentation/kernel-parameters.txt
>> @@ -343,6 +343,9 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>> no: ACPI OperationRegions are not marked as reserved,
>> no further checks are performed.
>>
>> + acpi_no_memhotplug [ACPI] Disable memory hotplug. Useful for kexec
>> + and kdump kernels.
>> +
>> add_efi_memmap [EFI; X86] Include EFI memory map in
>> kernel's map of available physical RAM.
>>
>> diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
>> index 551dad7..4a0fa94 100644
>> --- a/drivers/acpi/acpi_memhotplug.c
>> +++ b/drivers/acpi/acpi_memhotplug.c
>> @@ -361,7 +361,19 @@ static void acpi_memory_device_remove(struct acpi_device *device)
>> acpi_memory_device_free(mem_device);
>> }
>>
>> +static bool acpi_no_memhotplug;
>> +
>
> I think this should be annotated with __initdata.
Yep, I'll shoot out a v4 with that change.
P.
>
>> void __init acpi_memory_hotplug_init(void)
>> {
>> + if (acpi_no_memhotplug)
>> + return;
>> +
>> acpi_scan_add_handler_with_hotplug(&memory_device_handler, "memory");
>> }
>> +
>> +static int __init disable_acpi_memory_hotplug(char *str)
>> +{
>> + acpi_no_memhotplug = true;
>> + return 1;
>> +}
>> +__setup("acpi_no_memhotplug", disable_acpi_memory_hotplug);
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Prarit Bhargava <prarit@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-kernel@vger.kernel.org, Vivek Goyal <vgoyal@redhat.com>,
Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
kosaki.motohiro@gmail.com, dyoung@redhat.com, toshi.kani@hp.com,
isimatu.yasuaki@jp.fujitsu.com, linux-acpi@vger.kernel.org,
kexec@lists.infradead.org
Subject: Re: [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v3]
Date: Wed, 15 Jan 2014 06:21:47 -0500 [thread overview]
Message-ID: <52D66F4B.8080301@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1401141642020.3375@chino.kir.corp.google.com>
On 01/14/2014 07:42 PM, David Rientjes wrote:
> On Tue, 14 Jan 2014, Prarit Bhargava wrote:
>
>> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
>> index b9e9bd8..ea93f75 100644
>> --- a/Documentation/kernel-parameters.txt
>> +++ b/Documentation/kernel-parameters.txt
>> @@ -343,6 +343,9 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>> no: ACPI OperationRegions are not marked as reserved,
>> no further checks are performed.
>>
>> + acpi_no_memhotplug [ACPI] Disable memory hotplug. Useful for kexec
>> + and kdump kernels.
>> +
>> add_efi_memmap [EFI; X86] Include EFI memory map in
>> kernel's map of available physical RAM.
>>
>> diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
>> index 551dad7..4a0fa94 100644
>> --- a/drivers/acpi/acpi_memhotplug.c
>> +++ b/drivers/acpi/acpi_memhotplug.c
>> @@ -361,7 +361,19 @@ static void acpi_memory_device_remove(struct acpi_device *device)
>> acpi_memory_device_free(mem_device);
>> }
>>
>> +static bool acpi_no_memhotplug;
>> +
>
> I think this should be annotated with __initdata.
Yep, I'll shoot out a v4 with that change.
P.
>
>> void __init acpi_memory_hotplug_init(void)
>> {
>> + if (acpi_no_memhotplug)
>> + return;
>> +
>> acpi_scan_add_handler_with_hotplug(&memory_device_handler, "memory");
>> }
>> +
>> +static int __init disable_acpi_memory_hotplug(char *str)
>> +{
>> + acpi_no_memhotplug = true;
>> + return 1;
>> +}
>> +__setup("acpi_no_memhotplug", disable_acpi_memory_hotplug);
next prev parent reply other threads:[~2014-01-15 11:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 19:21 [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v3] Prarit Bhargava
2014-01-14 19:21 ` Prarit Bhargava
2014-01-14 19:21 ` Prarit Bhargava
2014-01-14 19:24 ` Vivek Goyal
2014-01-14 19:24 ` Vivek Goyal
2014-01-14 19:24 ` Vivek Goyal
2014-01-15 0:42 ` David Rientjes
2014-01-15 0:42 ` David Rientjes
2014-01-15 11:21 ` Prarit Bhargava [this message]
2014-01-15 11:21 ` Prarit Bhargava
2014-01-15 12:34 ` [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v4] Prarit Bhargava
2014-01-15 12:34 ` Prarit Bhargava
2014-01-15 12:34 ` Prarit Bhargava
2014-01-15 13:47 ` Rafael J. Wysocki
2014-01-15 13:47 ` Rafael J. Wysocki
2014-01-15 16:39 ` Vivek Goyal
2014-01-15 16:39 ` Vivek Goyal
2014-01-15 20:48 ` David Rientjes
2014-01-15 20:48 ` David Rientjes
2014-01-15 21:51 ` Toshi Kani
2014-01-15 21:51 ` Toshi Kani
2014-01-15 21:51 ` Toshi Kani
2014-01-16 15:35 ` [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v5] Prarit Bhargava
2014-01-16 15:35 ` Prarit Bhargava
2014-01-16 15:35 ` Prarit Bhargava
2014-01-16 23:24 ` David Rientjes
2014-01-16 23:24 ` David Rientjes
2014-01-17 1:26 ` Rafael J. Wysocki
2014-01-17 1:26 ` Rafael J. Wysocki
2014-01-17 1:15 ` Prarit Bhargava
2014-01-17 1:15 ` Prarit Bhargava
2014-01-15 1:17 ` [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v3] Dave Young
2014-01-15 1:17 ` Dave Young
2014-01-15 1:17 ` Dave Young
2014-01-15 3:43 ` Yasuaki Ishimatsu
2014-01-15 3:43 ` Yasuaki Ishimatsu
2014-01-15 3:43 ` Yasuaki Ishimatsu
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=52D66F4B.8080301@redhat.com \
--to=prarit@redhat.com \
--cc=dyoung@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.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=rientjes@google.com \
--cc=rjw@rjwysocki.net \
--cc=toshi.kani@hp.com \
--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 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.