From: "Luck, Tony" <tony.luck@intel.com>
To: James Dingwall <james@dingwall.me.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>
Subject: RE: pstore does not work under xen
Date: Thu, 19 Sep 2019 15:51:33 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7F472015@ORSMSX115.amr.corp.intel.com> (raw)
In-Reply-To: <20190919102643.GA9400@dingwall.me.uk>
> I have been investigating a regression in our environment where pstore
> (efi-pstore specifically but I suspect this would affect all
> implementations) no longer works after upgrading from a 4.4 to 5.0
> kernel when running under xen. (This is an Ubuntu kernel but I don't
> think there are patches which affect this area.)
I don't have any answer for this ... but want to throw out the idea that
VMM systems could provide some hypercalls to guests to save/return
some blob of memory (perhaps the "save" triggers automagically if the
guest crashes?).
That would provide a much better pstore back end than relying on emulation
of EFI persistent variables (which have severe contraints on size, and don't
support some pstore modes because you can't dynamically update EFI variables
hundreds of times per second).
-Tony
next prev parent reply other threads:[~2019-09-19 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 10:26 pstore does not work under xen James Dingwall
2019-09-19 15:51 ` Luck, Tony [this message]
2019-09-19 16:14 ` James Dingwall
2019-09-19 16:37 ` Boris Ostrovsky
2019-09-23 15:42 ` James Dingwall
2019-09-23 22:59 ` Kees Cook
2019-09-24 0:41 ` Boris Ostrovsky
2019-09-25 11:01 ` James Dingwall
2019-09-25 15:38 ` Boris Ostrovsky
2019-09-25 15:38 ` [Xen-devel] " Boris Ostrovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3908561D78D1C84285E8C5FCA982C28F7F472015@ORSMSX115.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=anton@enomsg.org \
--cc=boris.ostrovsky@oracle.com \
--cc=ccross@android.com \
--cc=james@dingwall.me.uk \
--cc=jgross@suse.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.