From: Florian Weimer <fweimer@redhat.com>
To: Ram Pai <linuxram@us.ibm.com>, mpe@ellerman.id.au
Cc: Ulrich.Weigand@de.ibm.com, mhocko@kernel.org,
dave.hansen@intel.com, aneesh.kumar@linux.vnet.ibm.com,
luto@kernel.org, bauerman@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 5/5] powerpc/pkeys: make protection key 0 less special
Date: Tue, 12 Jun 2018 14:18:22 +0200 [thread overview]
Message-ID: <c70afc10-9ad4-c5ec-6773-7f0ef455dced@redhat.com> (raw)
In-Reply-To: <1528164594-23823-6-git-send-email-linuxram@us.ibm.com>
On 06/05/2018 04:09 AM, Ram Pai wrote:
> diff --git a/arch/powerpc/include/asm/pkeys.h b/arch/powerpc/include/asm/pkeys.h
> index 0409c80..d349e22 100644
> --- a/arch/powerpc/include/asm/pkeys.h
> +++ b/arch/powerpc/include/asm/pkeys.h
> @@ -13,7 +13,10 @@
>
> DECLARE_STATIC_KEY_TRUE(pkey_disabled);
> extern int pkeys_total; /* total pkeys as per device tree */
> -extern u32 initial_allocation_mask; /* bits set for reserved keys */
> +extern u32 initial_allocation_mask; /* bits set for the initially allocated keys */
> +extern u32 reserved_allocation_mask; /* bits set for reserved keys */
> +
> +#define PKEY_0 0
>
> /*
> * Define these here temporarily so we're not dependent on patching linux/mm.h.
This part no longer applies cleanly.
Thanks,
Florian
prev parent reply other threads:[~2018-06-12 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 2:09 [PATCH 0/5] powerpc/pkeys: fixes to pkeys Ram Pai
2018-06-05 2:09 ` [PATCH 1/5] powerpc/pkeys: Enable all user-allocatable pkeys at init Ram Pai
2018-06-05 2:09 ` [PATCH 2/5] powerpc/pkeys: Save the pkey registers before fork Ram Pai
2018-06-05 2:09 ` [PATCH 3/5] powerpc/pkeys: fix calculation of total pkeys Ram Pai
2018-06-05 2:09 ` [PATCH 4/5] powerpc/pkeys: Preallocate execute-only key Ram Pai
2018-06-05 2:09 ` [PATCH 5/5] powerpc/pkeys: make protection key 0 less special Ram Pai
2018-06-12 12:18 ` Florian Weimer [this message]
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=c70afc10-9ad4-c5ec-6773-7f0ef455dced@redhat.com \
--to=fweimer@redhat.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bauerman@linux.vnet.ibm.com \
--cc=dave.hansen@intel.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=luto@kernel.org \
--cc=mhocko@kernel.org \
--cc=mpe@ellerman.id.au \
/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).