Date: Thu, 3 Jul 2008 15:14:56 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Bernhard Walle <bwalle@suse.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
       Vivek Goyal <vgoyal@redhat.com>, x86@kernel.org,
       kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Find offset for crashkernel reservation
	automatically
Message-ID: <20080703131456.GA12102@elte.hu>
References: <1214510048-21215-1-git-send-email-bwalle@suse.de> <20080627133256.GB5801@redhat.com> <20080627134212.GC5801@redhat.com> <20080627160656.06f71661@halley.suse.de> <20080627141910.GD5801@redhat.com> <20080627162223.2df5a8b9@halley.suse.de> <m1zlp6vjub.fsf@frodo.ebiederm.org> <20080627202932.16634031@kopernikus.site>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080627202932.16634031@kopernikus.site>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 881
Lines: 23


* Bernhard Walle <bwalle@suse.de> wrote:

> > > But in general policy should go in userspace (if possible), so I 
> > > agree with you that kexec-tools can handle that.
> > 
> > At a quick skim the patch looks good.  I thought I had initially 
> > implemented the code to work this way but apparently in all of the 
> > churn that aspect of it got lost.
> > 
> > Let's start with trying to allocate the memory as low as possible 
> > for a crash kernel (I think you are already doing that).
> 
> Yes, in 95 % of the cases the crashkernel still gets reserved at 16M.

ok - i've applied it to tip/x86/crashdump - thanks Bernhard.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/