[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110716202753.GA16161@srcf.ucam.org>
Date: Sat, 16 Jul 2011 21:27:53 +0100
From: Matthew Garrett <mjg@...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>,
Vivek Goyal <vgoyal@...hat.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Americo Wang <xiyou.wangcong@...il.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 01:11:47PM -0700, Eric W. Biederman wrote:
> Without some real understanding of what is going on I'm not inclined
> to meet any of this half way and summarily reject every change to
> the kexec on panic code path.
There are platforms that simply refuse to correctly function with a 1:1
physical/virtual mapping. But that's not the point here - this patch
simply hardcodes saving dmesg to an EFI variable rather than using
kmsg_dump and pstore in order to avoid handling the locking, and does
nothing whatsoever to change the amount of EFI code involved.
--
Matthew Garrett | mjg59@...f.ucam.org
--
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