All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: kexec@lists.infradead.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	kosaki.motohiro@gmail.com, dyoung@redhat.com,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v2]
Date: Fri, 10 Jan 2014 09:49:10 -0500	[thread overview]
Message-ID: <20140110144910.GB19115@redhat.com> (raw)
In-Reply-To: <1389364615-13320-1-git-send-email-prarit@redhat.com>

On Fri, Jan 10, 2014 at 09:36:55AM -0500, Prarit Bhargava wrote:

[..]
> This can also be reproduced by using the memmap=exactmap and mem=X
> parameters on the main kernel and booting.
> 
> This patchset resolves the problem by adding a kernel parameter,
> acpi_no_memhotplug, to disable ACPI memory hotplug.

Hi Prarit,

People seem to like the idea of disabling hotplug automatically if
memmap=exactmap or mem=X is passed on command line. Can you please take
care of that too. That way we would not have to modify kexec-tools and
kernel update will fix this issue.

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Prarit Bhargava <prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	"Rafael J. Wysocki" <rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	kosaki.motohiro-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v2]
Date: Fri, 10 Jan 2014 09:49:10 -0500	[thread overview]
Message-ID: <20140110144910.GB19115@redhat.com> (raw)
In-Reply-To: <1389364615-13320-1-git-send-email-prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Fri, Jan 10, 2014 at 09:36:55AM -0500, Prarit Bhargava wrote:

[..]
> This can also be reproduced by using the memmap=exactmap and mem=X
> parameters on the main kernel and booting.
> 
> This patchset resolves the problem by adding a kernel parameter,
> acpi_no_memhotplug, to disable ACPI memory hotplug.

Hi Prarit,

People seem to like the idea of disabling hotplug automatically if
memmap=exactmap or mem=X is passed on command line. Can you please take
care of that too. That way we would not have to modify kexec-tools and
kernel update will fix this issue.

Thanks
Vivek

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, Len Brown <lenb@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	kosaki.motohiro@gmail.com, dyoung@redhat.com,
	linux-acpi@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v2]
Date: Fri, 10 Jan 2014 09:49:10 -0500	[thread overview]
Message-ID: <20140110144910.GB19115@redhat.com> (raw)
In-Reply-To: <1389364615-13320-1-git-send-email-prarit@redhat.com>

On Fri, Jan 10, 2014 at 09:36:55AM -0500, Prarit Bhargava wrote:

[..]
> This can also be reproduced by using the memmap=exactmap and mem=X
> parameters on the main kernel and booting.
> 
> This patchset resolves the problem by adding a kernel parameter,
> acpi_no_memhotplug, to disable ACPI memory hotplug.

Hi Prarit,

People seem to like the idea of disabling hotplug automatically if
memmap=exactmap or mem=X is passed on command line. Can you please take
care of that too. That way we would not have to modify kexec-tools and
kernel update will fix this issue.

Thanks
Vivek

  reply	other threads:[~2014-01-10 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 14:36 [PATCH] acpi memory hotplug, add parameter to disable memory hotplug [v2] Prarit Bhargava
2014-01-10 14:36 ` Prarit Bhargava
2014-01-10 14:36 ` Prarit Bhargava
2014-01-10 14:49 ` Vivek Goyal [this message]
2014-01-10 14:49   ` Vivek Goyal
2014-01-10 14:49   ` Vivek Goyal
2014-01-10 14:55   ` Prarit Bhargava
2014-01-10 14:55     ` 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=20140110144910.GB19115@redhat.com \
    --to=vgoyal@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=prarit@redhat.com \
    --cc=rjw@rjwysocki.net \
    /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.