From: Dave Hansen <dave.hansen@intel.com>
To: Florian Weimer <fweimer@redhat.com>,
linux-api@vger.kernel.org, linux-mm@kvack.org
Cc: linuxram@us.ibm.com
Subject: Re: pkeys: Reserve PKEY_DISABLE_READ
Date: Thu, 8 Nov 2018 06:57:51 -0800 [thread overview]
Message-ID: <2d62c9e2-375b-2791-32ce-fdaa7e7664fd@intel.com> (raw)
In-Reply-To: <877ehnbwqy.fsf@oldenburg.str.redhat.com>
On 11/8/18 4:05 AM, Florian Weimer wrote:
> Would it be possible to reserve a bit for PKEY_DISABLE_READ?
>
> I think the POWER implementation can disable read access at the hardware
> level, but not write access, and that cannot be expressed with the
> current PKEY_DISABLE_ACCESS and PKEY_DISABLE_WRITE bits.
Do you just mean in the syscall interfaces? What would we need to do on
x86 if we see the bit? Would we just say it's invalid on x86, or would
we make sure that PKEY_DISABLE_ACCESS==PKEY_DISABLE_READ?
next prev parent reply other threads:[~2018-11-08 14:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 12:05 Florian Weimer
2018-11-08 14:57 ` Dave Hansen [this message]
2018-11-08 15:01 ` Florian Weimer
2018-11-08 17:14 ` Dave Hansen
2018-11-08 17:37 ` Florian Weimer
2018-11-08 20:12 ` Ram Pai
2018-11-08 20:23 ` Florian Weimer
2018-11-09 18:09 ` Ram Pai
2018-11-12 12:00 ` Florian Weimer
2018-11-27 10:23 ` Ram Pai
2018-11-27 11:57 ` Florian Weimer
2018-11-27 15:31 ` Dave Hansen
2018-11-29 11:37 ` Florian Weimer
2018-12-03 4:02 ` Ram Pai
2018-12-03 15:52 ` Florian Weimer
2018-12-04 6:23 ` Ram Pai
2018-12-05 13:00 ` Florian Weimer
2018-12-05 20:23 ` Ram Pai
2018-12-05 16:21 ` Andy Lutomirski
2018-12-05 20:36 ` Ram Pai
2018-11-08 20:08 ` Ram Pai
2018-11-08 20:11 ` Dave Hansen
2018-11-08 20:14 ` Florian Weimer
2018-11-08 19:22 ` Ram Pai
2018-11-12 10:29 ` Florian Weimer
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=2d62c9e2-375b-2791-32ce-fdaa7e7664fd@intel.com \
--to=dave.hansen@intel.com \
--cc=fweimer@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxram@us.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