From: Stefano Stabellini <sstabellini@kernel.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: Bertrand Marquis <Bertrand.Marquis@arm.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <stefanos@xilinx.com>,
George Dunlap <George.Dunlap@citrix.com>,
jgross@suse.com
Subject: Re: Runstate hypercall and Linux KPTI issues
Date: Thu, 10 Sep 2020 17:33:04 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2009100914300.28991@sstabellini-ThinkPad-T480s> (raw)
In-Reply-To: <b7c7b1c5-c7c0-d7c9-b300-9a26e3b73746@suse.com>
On Thu, 10 Sep 2020, Jan Beulich wrote:
> >>> - should we backport the support for this hypercall in older kernel releases ?
> >>
> >> It's a bug fix to KPTI, and as such ought to be at least eligible for
> >> considering doing so?
> >
> > That will mean also backport in Linux. What should be the scope ?
>
> All longterm and stable trees which are affected, as I think is usual.
From a Linux perspective, we should fix this as soon as possible: we
should backport a patch to make the usage of the runstate hypercall
conditional on KPTI being disabled on ARM.
Then, when available in Xen, we should backport the usage of the new
hypercall with a check to detect if it is available -- do not assume it
is available, users might not update Xen, but might update Linux.
We have to do this in two stages for a couple of reasons. It is best not
to wait for Xen-side changes to fix Linux any longer. And also, a Linux
fix is best implemented independently anyway: Linux should benefit from
the Xen improvements when available but not rely on their presence to
work.
next prev parent reply other threads:[~2020-09-11 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 13:46 Runstate hypercall and Linux KPTI issues Bertrand Marquis
2020-09-10 13:56 ` Jan Beulich
2020-09-10 14:00 ` Bertrand Marquis
2020-09-10 14:04 ` Bertrand Marquis
2020-09-10 14:08 ` Jan Beulich
2020-09-11 0:33 ` Stefano Stabellini [this message]
2020-09-24 17:25 ` Bertrand Marquis
2020-09-24 17:28 ` Bertrand Marquis
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=alpine.DEB.2.21.2009100914300.28991@sstabellini-ThinkPad-T480s \
--to=sstabellini@kernel.org \
--cc=Bertrand.Marquis@arm.com \
--cc=George.Dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=stefanos@xilinx.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).