From: Russell Currey <ruscur@russell.cc>
To: LEROY Christophe <christophe.leroy@c-s.fr>
Cc: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org, npiggin@gmail.com
Subject: Re: [PATCH 5/5] powerpc/64s: Document that PPC supports nosmap
Date: Mon, 29 Oct 2018 12:06:51 +1100 [thread overview]
Message-ID: <7b3e80077b4d9f22da891c143c78bb743cc24136.camel@russell.cc> (raw)
In-Reply-To: <20181026183525.Horde.tXUVv2_ZCCOci3XQBF4ZYw1@messagerie.si.c-s.fr>
On Fri, 2018-10-26 at 18:35 +0200, LEROY Christophe wrote:
> Why not call our new functionnality SMAP instead of calling it GUAP ?
mpe wasn't a fan of using the same terminology as other architectures.
Having a separate term does avoid some assumptions about how things
work or are implemented, but sharing compatibility with an existing
parameter is nice.
Personally I don't really care too much about the name.
- Russell
>
> Christophe
>
> Russell Currey <ruscur@russell.cc> a écrit :
>
> > Signed-off-by: Russell Currey <ruscur@russell.cc>
> > ---
> > Documentation/admin-guide/kernel-parameters.txt | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt
> > b/Documentation/admin-guide/kernel-parameters.txt
> > index a5ad67d5cb16..8f78e75965f0 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -2764,7 +2764,7 @@
> > noexec=on: enable non-executable mappings
> > (default)
> > noexec=off: disable non-executable mappings
> >
> > - nosmap [X86]
> > + nosmap [X86,PPC]
> > Disable SMAP (Supervisor Mode Access
> > Prevention)
> > even if it is supported by processor.
> >
> > --
> > 2.19.1
>
>
next prev parent reply other threads:[~2018-10-29 1:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 6:35 [PATCH 0/5] Guarded Userspace Access Prevention on Radix Russell Currey
2018-10-26 6:35 ` [PATCH 1/5] powerpc/64s: Guarded Userspace Access Prevention Russell Currey
2018-10-26 8:20 ` kbuild test robot
2018-10-28 17:57 ` LEROY Christophe
2018-10-31 4:00 ` Russell Currey
2018-10-31 16:54 ` LEROY Christophe
2018-10-29 13:27 ` kbuild test robot
2018-10-26 6:35 ` [PATCH 2/5] powerpc/futex: GUAP support for futex ops Russell Currey
2018-10-26 16:32 ` LEROY Christophe
2018-10-29 1:08 ` Russell Currey
2018-10-26 6:35 ` [PATCH 3/5] powerpc/lib: checksum GUAP support Russell Currey
2018-10-26 16:33 ` LEROY Christophe
2018-10-26 6:35 ` [PATCH 4/5] powerpc/64s: Disable GUAP with nosmap option Russell Currey
2018-10-26 6:35 ` [PATCH 5/5] powerpc/64s: Document that PPC supports nosmap Russell Currey
2018-10-26 16:35 ` LEROY Christophe
2018-10-29 1:06 ` Russell Currey [this message]
2018-10-31 17:06 ` LEROY Christophe
2018-10-26 16:29 ` [PATCH 0/5] Guarded Userspace Access Prevention on Radix LEROY Christophe
2018-10-31 3:53 ` Russell Currey
2018-10-31 16:58 ` LEROY Christophe
2018-11-01 3:54 ` Russell Currey
2018-11-08 17:52 ` Christophe LEROY
2018-11-08 20:09 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2018-10-17 6:44 [PATCH 1/5] powerpc/64s: Kernel Hypervisor Restricted Access Prevention Russell Currey
2018-10-17 6:44 ` [PATCH 5/5] powerpc/64s: Document that PPC supports nosmap Russell Currey
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=7b3e80077b4d9f22da891c143c78bb743cc24136.camel@russell.cc \
--to=ruscur@russell.cc \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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).