[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131017120519.GF10834@console-pimps.org>
Date: Thu, 17 Oct 2013 13:05:19 +0100
From: Matt Fleming <matt@...sole-pimps.org>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: Matthew Garrett <mjg59@...f.ucam.org>,
"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
On Wed, 16 Oct, at 02:52:25PM, Luck, Tony wrote:
> > 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.
I admit that using kexec with the EFI capsule + pstore code is not
something I'd considered. Though as you say, if you manage to jump to
your crash kernel I'm not sure how much use the capsule would be.
--
Matt Fleming, Intel Open Source Technology Center
--
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