From: Shawn Anastasio <shawn@anastas.io>
To: linuxppc-dev@lists.ozlabs.org
Cc: npiggin@gmail.com
Subject: [PATCH 0/2] Reintroduce PROT_SAO
Date: Thu, 20 Aug 2020 20:08:35 -0500 [thread overview]
Message-ID: <20200821010837.4079-1-shawn@anastas.io> (raw)
This set re-introduces the PROT_SAO prot flag removed in
Commit 5c9fa16e8abd ("powerpc/64s: Remove PROT_SAO support").
To address concerns regarding live migration of guests using SAO
to P10 hosts without SAO support, the flag is disabled by default
in LPARs. A new config option, PPC_PROT_SAO_LPAR was added to
allow users to explicitly enable it if they will not be running
in an environment where this is a conern.
Shawn Anastasio (2):
Revert "powerpc/64s: Remove PROT_SAO support"
powerpc/64s: Disallow PROT_SAO in LPARs by default
arch/powerpc/Kconfig | 12 ++++++
arch/powerpc/include/asm/book3s/64/pgtable.h | 8 ++--
arch/powerpc/include/asm/cputable.h | 10 ++---
arch/powerpc/include/asm/mman.h | 31 ++++++++++++--
arch/powerpc/include/asm/nohash/64/pgtable.h | 2 +
arch/powerpc/include/uapi/asm/mman.h | 2 +-
arch/powerpc/kernel/dt_cpu_ftrs.c | 2 +-
arch/powerpc/mm/book3s64/hash_utils.c | 2 +
include/linux/mm.h | 2 +
include/trace/events/mmflags.h | 2 +
mm/ksm.c | 4 ++
tools/testing/selftests/powerpc/mm/.gitignore | 1 +
tools/testing/selftests/powerpc/mm/Makefile | 4 +-
tools/testing/selftests/powerpc/mm/prot_sao.c | 42 +++++++++++++++++++
14 files changed, 107 insertions(+), 17 deletions(-)
create mode 100644 tools/testing/selftests/powerpc/mm/prot_sao.c
--
2.28.0
next reply other threads:[~2020-08-21 1:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 1:08 Shawn Anastasio [this message]
2020-08-21 1:08 ` [PATCH 1/2] Revert "powerpc/64s: Remove PROT_SAO support" Shawn Anastasio
2020-08-21 1:08 ` [PATCH 2/2] powerpc/64s: Disallow PROT_SAO in LPARs by default Shawn Anastasio
2020-08-21 10:37 ` Nicholas Piggin
2020-08-21 18:55 ` Shawn Anastasio
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=20200821010837.4079-1-shawn@anastas.io \
--to=shawn@anastas.io \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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).