[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131024192446.GF2322@redhat.com>
Date: Thu, 24 Oct 2013 15:24:46 -0400
From: Vivek Goyal <vgoyal@...hat.com>
To: Yinghai Lu <yinghai@...nel.org>
Cc: WANG Chao <chaowang@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Pekka Enberg <penberg@...nel.org>,
Jacob Shin <jacob.shin@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86, kdump: crashkernel=X try to reserve below 896M
first, then try below 4G, then MAXMEM
On Thu, Oct 24, 2013 at 12:13:41PM -0700, Yinghai Lu wrote:
[..]
> old kexec-tools could work cross 892M in some case.
> That will confuse the user,
If it could work beyong 892MB, then why are you limiting user to 896MB
only. That sounds wrong.
> as it works some time on some setup, but does
> not work on other setup.
If it can work above 896MB, then those other setup should be fixed.
All the existing users of crashkernel=xM *will not* be affected by this
change. Memory reservation will still be below 892MB.
Memory reservation will gove above 896MB, only if user chooses to reserve
more memory. If kexec works in that case, its a win-win situation. If it
does not and fails, then it is status quo is maintained.
Thanks
Vivek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists