[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F31D31122@ORSMSX106.amr.corp.intel.com>
Date: Wed, 16 Oct 2013 14:52:25 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Matthew Garrett <mjg59@...f.ucam.org>,
Matt Fleming <matt@...sole-pimps.org>
CC: "linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andi Kleen <ak@...ux.intel.com>,
Seiji Aguchi <seiji.aguchi@....com>,
"x86@...nel.org" <x86@...nel.org>,
"Fleming, Matt" <matt.fleming@...el.com>
Subject: RE: [PATCH 5/5] efi: Capsule update support and pstore backend
> Where by "May not function correctly" you mean "May crash the system"?
> I'm a little uneasy having this run by default if enabled, even if it's
> disabled by default in the config.
There's also an "either/or" choice between using efi-capsule with pstore, and the
traditional kexec/kdump method for getting a memory dump from a crash. We
have to go through a reset to save the capsule - but we don't want a reset for
kexec. Perhaps we can pass the reset parameters through the kexec path to
the new kernel to make it do the right kind of reset ... but the value of the capsule
dump is minimal if kdump managed to dump everything.
Bottom line: users need to make an informed choice to use efi-capsule + pstore.
-Tony
--
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