[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110718114334.GA31986@redhat.com>
Date: Mon, 18 Jul 2011 07:43:34 -0400
From: Vivek Goyal <vgoyal@...hat.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Seiji Aguchi <seiji.aguchi@....com>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Americo Wang <xiyou.wangcong@...il.com>,
Matthew Garrett <mjg@...hat.com>,
"tony.luck@...el.com" <tony.luck@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jarod Wilson <jwilson@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"dle-develop@...ts.sourceforge.net"
<dle-develop@...ts.sourceforge.net>,
Satoru Moriya <satoru.moriya@....com>
Subject: Re: [RFC][PATCH] Replace a function call chain of
kmsg_dump(KMSG_DUMP_KEXEC) with static function calls
On Sat, Jul 16, 2011 at 09:16:06AM -0700, Eric W. Biederman wrote:
[..]
> Am I wrong in thinking that the core motivation behind this patch is
> that our EFI support sucks and thus kdump on EFI does not work on some
> platforms?
One of the arguments seems is that kdump might not work 100% of the
time and saving kernel messages atleast gets some information out
reliably.
I think being able to save dmesg to NVRAM, in general sounds good to
me (if done in a relatively clean manner). Especially if we can get
rid of code taking locks and code path executed after crash is not
tool long and relatively easy to audit.
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