From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: "Naveen N . Rao" <naveen.n.rao@linux.vnet.ibm.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Nicholas Piggin" <npiggin@gmail.com>
Subject: [RFC PATCH 0/2] 2nd attempt at PR KVM + SCV and syscall
Date: Tue, 18 Jan 2022 15:58:19 +1000 [thread overview]
Message-ID: <20220118055821.3065241-1-npiggin@gmail.com> (raw)
The more I looked into system call emulation, the harder it seems to
get.
Second proposal is remove it entirely because it's already broken, and
just boot-time restrict SCV support if we run with PR possible, in hash
mode, on pseries. Unfortunately that catches Power9 PowerVM, but at
least OpenPOWER and Power10 by default is okay.
We probably have to do this as a minimal backport at first even if we
did later decide we need to fix things in a better way because it looks
like it would take a lot of work.
Any comments? mpe helped with looking at the tracing logic and history
of the code (thanks) but any mistakes are mine, Naveen are we on the
right track here?
Thanks,
Nick
Nicholas Piggin (2):
powerpc/64: remove system call instruction emulation
KVM: PPC: Book3S PR: Disable SCV when running AIL is disabled
arch/powerpc/kernel/exceptions-64s.S | 4 ++++
arch/powerpc/kernel/setup_64.c | 15 ++++++++++++
arch/powerpc/kvm/book3s_pr.c | 20 +++++++++++-----
arch/powerpc/lib/sstep.c | 36 ----------------------------
4 files changed, 33 insertions(+), 42 deletions(-)
--
2.23.0
next reply other threads:[~2022-01-18 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 5:58 Nicholas Piggin [this message]
2022-01-18 5:58 ` [RFC PATCH 1/2] powerpc/64: remove system call instruction emulation Nicholas Piggin
2022-01-19 17:46 ` Naveen N. Rao
2022-01-18 5:58 ` [RFC PATCH 2/2] KVM: PPC: Book3S PR: Disable SCV when running AIL is disabled Nicholas Piggin
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=20220118055821.3065241-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=clg@kaod.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
/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).