From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 0/3] xen/pv: sanitize xen pv guest msr accesses
Date: Mon, 26 Sep 2022 16:18:46 +0200 [thread overview]
Message-ID: <20220926141849.21805-1-jgross@suse.com> (raw)
Historically when running as Xen PV guest all MSR accesses have been
silently swallowing any GP faults, even when the kernel was using not
the *msr_safe() access functions.
Change that by making the behavior controllable via kernel config and
via a boot parameter.
This will help finding paths where MSRs are being accessed under Xen
which are not emulated by the hypervisor.
Juergen Gross (3):
xen/pv: allow pmu msr accesses to cause GP
xen/pv: refactor msr access functions to support safe and unsafe
accesses
xen/pv: support selecting safe/unsafe msr accesses
.../admin-guide/kernel-parameters.txt | 6 ++
arch/x86/xen/Kconfig | 9 ++
arch/x86/xen/enlighten_pv.c | 97 +++++++++++++------
arch/x86/xen/pmu.c | 44 +++++----
4 files changed, 110 insertions(+), 46 deletions(-)
--
2.35.3
next reply other threads:[~2022-09-26 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 14:18 Juergen Gross [this message]
2022-09-26 14:18 ` [PATCH 1/3] xen/pv: allow pmu msr accesses to cause GP Juergen Gross
2022-09-26 15:29 ` Jan Beulich
2022-09-26 15:33 ` Juergen Gross
2022-09-26 20:09 ` Boris Ostrovsky
2022-09-27 5:42 ` Juergen Gross
2022-09-26 14:18 ` [PATCH 2/3] xen/pv: refactor msr access functions to support safe and unsafe accesses Juergen Gross
2022-09-26 14:18 ` [PATCH 3/3] xen/pv: support selecting safe/unsafe msr accesses Juergen Gross
2022-09-26 15:23 ` Jan Beulich
2022-09-26 15:36 ` Juergen Gross
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=20220926141849.21805-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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).