[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5285DD15.6080700@iki.fi>
Date: Fri, 15 Nov 2013 10:36:37 +0200
From: Pekka Enberg <penberg@....fi>
To: jerry.hoemann@...com, Pekka Enberg <penberg@...nel.org>
CC: "H. Peter Anvin" <hpa@...or.com>, Rob Landley <rob@...dley.net>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
x86 maintainers <x86@...nel.org>,
Matt Fleming <matt.fleming@...el.com>,
Yinghai Lu <yinghai@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"list@...ederm.org:DOCUMENTATION" <linux-doc@...r.kernel.org>,
"list@...ederm.org:MEMORY MANAGEMENT" <linux-mm@...ck.org>,
linux-doc@...r.kernel.org, linux-efi@...r.kernel.org,
Vivek Goyal <vgoyal@...hat.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] Early use of boot service memory
On 11/15/13 2:50 AM, jerry.hoemann@...com wrote:
> One already has to specify command line arguments to enable kdump.
Yes, so what?
The problem with your patch is that now to enable kdump, I have to know
that there's a second command line option and if my firmware is "broken"
or not. The former is already a problem (how do I even know such a
thing exists?) but the latter is almost impossible to solve from user
point of view. And if I have a "broken" firmware, kdump won't work no
matter what options I pass.
I really don't see what's practical about that.
Pekka
--
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