From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Han, Huaitong" <huaitong.han@intel.com>
Cc: "jbeulich@suse.com" <jbeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [V2 PATCH 0/9] x86/hvm: pkeys, add memory protection-key support
Date: Fri, 27 Nov 2015 16:31:33 +0000 [thread overview]
Message-ID: <56588565.8010109@citrix.com> (raw)
In-Reply-To: <1448641320.7592.13.camel@intel.com>
On 27/11/15 16:22, Han, Huaitong wrote:
> On Fri, 2015-11-27 at 12:59 +0000, Andrew Cooper wrote:
>> Just for my own understand, do you have a sample use-case for
>> protection
>> keys?
>>
>> As everything can WRPKRU, I cant see how it would actually be useful.
>> Clearly there is a usecase or you (Intel) wouldn't have gone to the
>> effort of putting into silicon.
>>
>> ~Andrew
> I understand PKU is a active memory protection, pkru register is thread
> -private, every thread can only change its pkru value, it is a
> enhancement of pte write/access, it provides two advantage:
> 1.During permission changes, we only need update pkru register instead
> of pte, so it can reduce the need to perform TLB shootdowns.
> 2.Compared with traditional read and write permissions, it can provide
> thread-private permissions.
So it is a feature which allows threads to cooperatively prevent
themselves trampling on each other.
I can see this being useful for debugging and robustness.
~Andrew
prev parent reply other threads:[~2015-11-27 16:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 9:51 [V2 PATCH 0/9] x86/hvm: pkeys, add memory protection-key support Huaitong Han
2015-11-27 9:51 ` [V2 PATCH 1/9] x86/hvm: pkeys, add pkeys support for cpuid handling Huaitong Han
2015-12-01 20:03 ` Andrew Cooper
2015-12-02 11:06 ` Jan Beulich
2015-12-03 1:53 ` Han, Huaitong
2015-12-03 10:41 ` Jan Beulich
2015-12-02 11:19 ` Jan Beulich
2015-11-27 9:51 ` [V2 PATCH 2/9] x86/hvm: pkeys, add the flag to enable Memory Protection Keys Huaitong Han
2015-12-01 20:04 ` Andrew Cooper
2015-12-02 11:21 ` Jan Beulich
2015-11-27 9:51 ` [V2 PATCH 3/9] x86/hvm: pkeys, add pkeys support when setting CR4 Huaitong Han
2015-12-01 20:05 ` Andrew Cooper
2015-11-27 9:51 ` [V2 PATCH 4/9] x86/hvm: pkeys, disable pkeys for guests in non-paging mode Huaitong Han
2015-11-27 9:51 ` [V2 PATCH 5/9] x86/hvm: pkeys, add functions to get pkeys value from PTE Huaitong Han
2015-12-01 20:11 ` Andrew Cooper
2015-12-02 11:24 ` Jan Beulich
2015-11-27 9:52 ` [V2 PATCH 6/9] x86/hvm: pkeys, add functions to support PKRU access Huaitong Han
2015-12-01 20:12 ` Andrew Cooper
2015-11-27 9:52 ` [V2 PATCH 7/9] x86/hvm: pkeys, add pkeys support for guest_walk_tables Huaitong Han
2015-12-01 20:30 ` Andrew Cooper
2015-12-02 8:23 ` Han, Huaitong
2015-12-02 11:14 ` Jan Beulich
2015-12-02 11:16 ` Jan Beulich
2015-12-02 11:29 ` Jan Beulich
2015-11-27 9:52 ` [V2 PATCH 8/9] x86/hvm: pkeys, add xstate support for pkeys Huaitong Han
2015-12-01 20:43 ` Andrew Cooper
2015-12-02 7:20 ` Han, Huaitong
2015-12-02 11:31 ` Jan Beulich
2015-12-03 1:58 ` Han, Huaitong
2015-12-03 10:42 ` Jan Beulich
2015-12-03 10:56 ` Andrew Cooper
2015-11-27 9:52 ` [V2 PATCH 9/9] x86/hvm: pkeys, add pkeys support for gva2gfn funcitons Huaitong Han
2015-12-02 11:35 ` Jan Beulich
2015-12-03 8:50 ` Han, Huaitong
2015-12-03 10:47 ` Jan Beulich
2015-11-27 12:59 ` [V2 PATCH 0/9] x86/hvm: pkeys, add memory protection-key support Andrew Cooper
2015-11-27 16:22 ` Han, Huaitong
2015-11-27 16:31 ` Andrew Cooper [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=56588565.8010109@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=huaitong.han@intel.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/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.