From: Dave Hansen <dave.hansen@intel.com>
To: Nayna Jain <nayna@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org,
Douglas Miller <dougmill@linux.vnet.ibm.com>,
Greg KH <gregkh@linuxfoundation.org>,
George Wilson <gcwilson@linux.ibm.com>,
gjoyce@ibm.com, Daniel Axtens <dja@axtens.net>,
"Weiny, Ira" <ira.weiny@intel.com>, Ram Pai <linuxram@us.ibm.com>
Subject: Re: [RFC PATCH 0/2] powerpc/pseries: add support for local secure storage called Platform Keystore(PKS)
Date: Tue, 1 Feb 2022 07:22:58 -0800 [thread overview]
Message-ID: <4d19936f-fc8a-8e86-95b2-67a4ab2e2b7f@intel.com> (raw)
In-Reply-To: <20220122005637.28199-1-nayna@linux.ibm.com>
On 1/21/22 16:56, Nayna Jain wrote:
> Nayna Jain (2):
> pseries: define driver for Platform Keystore
> pseries: define sysfs interface to expose PKS variables
Hi Folks,
There another feature that we might want to consider in the naming here:
> https://lore.kernel.org/all/20220127175505.851391-1-ira.weiny@intel.com/
Protection Keys for Supervisor pages is also called PKS. It's also not
entirely impossible that powerpc might want to start using this code at
some point, just like what happened with the userspace protection keys[1].
I don't think it's the end of the world either way, but it might save a
hapless user or kernel developer some confusion if we can avoid
including two "PKS" features in the kernel. I just wanted to make sure
we were aware of the other's existence. :)
1.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/include/asm/pkeys.h
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@intel.com>
To: Nayna Jain <nayna@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Greg KH <gregkh@linuxfoundation.org>,
Ram Pai <linuxram@us.ibm.com>,
linux-kernel@vger.kernel.org,
Douglas Miller <dougmill@linux.vnet.ibm.com>,
George Wilson <gcwilson@linux.ibm.com>,
"Weiny, Ira" <ira.weiny@intel.com>,
gjoyce@ibm.com, Daniel Axtens <dja@axtens.net>
Subject: Re: [RFC PATCH 0/2] powerpc/pseries: add support for local secure storage called Platform Keystore(PKS)
Date: Tue, 1 Feb 2022 07:22:58 -0800 [thread overview]
Message-ID: <4d19936f-fc8a-8e86-95b2-67a4ab2e2b7f@intel.com> (raw)
In-Reply-To: <20220122005637.28199-1-nayna@linux.ibm.com>
On 1/21/22 16:56, Nayna Jain wrote:
> Nayna Jain (2):
> pseries: define driver for Platform Keystore
> pseries: define sysfs interface to expose PKS variables
Hi Folks,
There another feature that we might want to consider in the naming here:
> https://lore.kernel.org/all/20220127175505.851391-1-ira.weiny@intel.com/
Protection Keys for Supervisor pages is also called PKS. It's also not
entirely impossible that powerpc might want to start using this code at
some point, just like what happened with the userspace protection keys[1].
I don't think it's the end of the world either way, but it might save a
hapless user or kernel developer some confusion if we can avoid
including two "PKS" features in the kernel. I just wanted to make sure
we were aware of the other's existence. :)
1.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/include/asm/pkeys.h
next prev parent reply other threads:[~2022-02-01 15:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 0:56 [RFC PATCH 0/2] powerpc/pseries: add support for local secure storage called Platform Keystore(PKS) Nayna Jain
2022-01-22 0:56 ` Nayna Jain
2022-01-22 0:56 ` [RFC PATCH 1/2] pseries: define driver for Platform Keystore Nayna Jain
2022-01-22 0:56 ` Nayna Jain
2022-01-22 0:56 ` [RFC PATCH 2/2] pseries: define sysfs interface to expose PKS variables Nayna Jain
2022-01-22 0:56 ` Nayna Jain
2022-02-09 9:13 ` Dov Murik
2022-02-09 9:13 ` Dov Murik
2022-01-22 7:29 ` [RFC PATCH 0/2] powerpc/pseries: add support for local secure storage called Platform Keystore(PKS) Greg KH
2022-01-22 7:29 ` Greg KH
2022-01-24 0:25 ` Daniel Axtens
2022-01-24 0:25 ` Daniel Axtens
2022-02-01 13:49 ` Greg KH
2022-02-01 13:49 ` Greg KH
2022-02-01 15:22 ` Dave Hansen [this message]
2022-02-01 15:22 ` Dave Hansen
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=4d19936f-fc8a-8e86-95b2-67a4ab2e2b7f@intel.com \
--to=dave.hansen@intel.com \
--cc=dja@axtens.net \
--cc=dougmill@linux.vnet.ibm.com \
--cc=gcwilson@linux.ibm.com \
--cc=gjoyce@ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=nayna@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.