From: Balbir Singh <bsingharora@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au
Cc: naveen.n.rao@linux.vnet.ibm.com, Balbir Singh <bsingharora@gmail.com>
Subject: [PATCH v1 0/3] Implement set_memory_xx for ppc64 book3s
Date: Tue, 1 Aug 2017 21:25:32 +1000 [thread overview]
Message-ID: <20170801112535.20765-1-bsingharora@gmail.com> (raw)
After implementing STRICT_KERNEL_RWX, it turns out that implementing
set_memory_ro/rw/x/nx is quite easy. The first patch is applied on
top (http://patchwork.ozlabs.org/patch/795745/).
The first patch implements the various routines, the second patch
enables ARCH_HAS_SET_MEMORY for PPC_BOOK3S_64 and the third patch
enables the BPF infrastructure to use the set_memory_ro and
set_memory_rw routines.
Balbir Singh (3):
arch/powerpc/set_memory: Implement set_memory_xx routines
Enable ARCH_HAS_SET_MEMORY
arch/powerpc/net/bpf: Basic EBPF support
arch/powerpc/Kconfig | 1 +
arch/powerpc/include/asm/book3s/64/hash.h | 6 +++
arch/powerpc/include/asm/book3s/64/radix.h | 6 +++
arch/powerpc/include/asm/set_memory.h | 34 +++++++++++++++
arch/powerpc/mm/pgtable-hash64.c | 51 ++++++++++++++++++++--
arch/powerpc/mm/pgtable-radix.c | 26 ++++++------
arch/powerpc/mm/pgtable_64.c | 68 ++++++++++++++++++++++++++++++
arch/powerpc/net/bpf_jit_comp64.c | 13 +-----
8 files changed, 177 insertions(+), 28 deletions(-)
create mode 100644 arch/powerpc/include/asm/set_memory.h
--
2.9.4
next reply other threads:[~2017-08-01 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 11:25 Balbir Singh [this message]
2017-08-01 11:25 ` [PATCH v1 1/3] arch/powerpc/set_memory: Implement set_memory_xx routines Balbir Singh
2017-08-01 19:08 ` christophe leroy
2017-08-02 3:07 ` Balbir Singh
2017-08-02 10:09 ` Aneesh Kumar K.V
2017-08-02 10:33 ` Balbir Singh
2017-08-04 3:38 ` Aneesh Kumar K.V
2017-08-04 3:53 ` Balbir Singh
2017-08-01 11:25 ` [PATCH v1 2/3] Enable ARCH_HAS_SET_MEMORY Balbir Singh
2017-08-01 11:25 ` [PATCH v1 3/3] arch/powerpc/net/bpf: Basic EBPF support Balbir Singh
2017-08-02 14:22 ` Naveen N. Rao
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=20170801112535.20765-1-bsingharora@gmail.com \
--to=bsingharora@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).