[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHD1Q_x8TQA7xMxbm0LaP-nBd0d++Ox7dQ9+2PsDfe3S+=nKHw@mail.gmail.com>
Date: Tue, 22 Sep 2020 14:04:30 -0300
From: "Guilherme G. Piccoli" <guilherme.piccoli@...onical.com>
To: boris.ostrovsky@...cle.com
Cc: Philipp Rudo <prudo@...ux.ibm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Baoquan He <bhe@...hat.com>,
kexec mailing list <kexec@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>,
Eric Biederman <ebiederm@...ssion.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Eric DeVolder <eric.devolder@...cle.com>,
Dave Young <dyoung@...hat.com>
Subject: Re: [PATCH] Only allow to set crash_kexec_post_notifiers on boot time
On Tue, Sep 22, 2020 at 11:53 AM <boris.ostrovsky@...cle.com> wrote:
>
>
> On 9/22/20 6:58 AM, Philipp Rudo wrote:
> >
> > AFAIK pstore requires UEFI to work. So what's the point to enable it on non-UEFI
> > systems?
>
>
> I don't think UEFI is required, ERST can specify its own backend. And that, in fact, can be quite useful in virtualization scenarios (especially in cases of direct boot, when there is no OVMF)
>
>
> -boris
There is ramoops backend too - I was able to collect a dmesg in a
cloud provider using that!
Powered by blists - more mailing lists