From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752296AbaAJOtl (ORCPT ); Fri, 10 Jan 2014 09:49:41 -0500 Received: from mx1.redhat.com ([209.132.183.28]:9995 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750931AbaAJOti (ORCPT ); Fri, 10 Jan 2014 09:49:38 -0500 Date: Fri, 10 Jan 2014 09:49:10 -0500 From: Vivek Goyal To: Prarit Bhargava Cc: linux-kernel@vger.kernel.org, Len Brown , "Rafael J. Wysocki" , 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] Message-ID: <20140110144910.GB19115@redhat.com> References: <1389364615-13320-1-git-send-email-prarit@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1389364615-13320-1-git-send-email-prarit@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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