From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH v2 0/2] KVM: PPC: Book3S PR: Fixes for AIL and SCV
Date: Sat, 29 Jan 2022 17:25:09 +1000 [thread overview]
Message-ID: <20220129072511.105523-1-npiggin@gmail.com> (raw)
The first patch in this series fixes a KVM PR host crash due to a
guest executing the scv instruction or with a pseries SMP host, the
host CPUs executing the scv instruction while a PR guest is running.
The second patch fixes unimplemented H_SET_MODE AIL modes by returning
failure from the hcall rather than succeeding but not implementing
the required behaviour. This works around missing host scv support for
scv-capable Linux guests by causing them to disable the facility.
Still looking at doing a proper capability for QEMU/KVM so we can get
consistency between HV, PR, and TCG. That shouldn't change these
patches though.
Thanks,
Nick
Nicholas Piggin (2):
KVM: PPC: Book3S PR: Disable SCV when AIL could be disabled
KVM: PPC: Book3S PR: Disallow AIL != 0
arch/powerpc/kernel/exceptions-64s.S | 4 ++++
arch/powerpc/kernel/setup_64.c | 28 ++++++++++++++++++++++++++++
arch/powerpc/kvm/Kconfig | 9 +++++++++
arch/powerpc/kvm/book3s_pr.c | 20 ++++++++++++++------
arch/powerpc/kvm/book3s_pr_papr.c | 20 ++++++++++++++++++++
5 files changed, 75 insertions(+), 6 deletions(-)
--
2.23.0
next reply other threads:[~2022-01-29 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 7:25 Nicholas Piggin [this message]
2022-01-29 7:25 ` [PATCH v2 1/2] KVM: PPC: Book3S PR: Disable SCV when AIL could be disabled Nicholas Piggin
2022-01-31 17:34 ` Fabiano Rosas
2022-02-02 13:09 ` kernel test robot
2022-01-29 7:25 ` [PATCH v2 2/2] KVM: PPC: Book3S PR: Disallow AIL != 0 Nicholas Piggin
2022-01-31 17:30 ` Fabiano Rosas
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=20220129072511.105523-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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).