All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Huaitong Han <huaitong.han@intel.com>, jbeulich@suse.com
Cc: xen-devel@lists.xen.org
Subject: Re: [V2 PATCH 5/9] x86/hvm: pkeys, add functions to get pkeys value from PTE
Date: Tue, 1 Dec 2015 20:11:24 +0000	[thread overview]
Message-ID: <565DFEEC.3060200@citrix.com> (raw)
In-Reply-To: <1448617923-10884-6-git-send-email-huaitong.han@intel.com>

On 27/11/15 09:51, Huaitong Han wrote:
> diff --git a/xen/include/asm-x86/x86_64/page.h b/xen/include/asm-x86/x86_64/page.h
> index 19ab4d0..49343ec 100644
> --- a/xen/include/asm-x86/x86_64/page.h
> +++ b/xen/include/asm-x86/x86_64/page.h
> @@ -134,6 +134,25 @@ typedef l4_pgentry_t root_pgentry_t;
>  #define get_pte_flags(x) (((int)((x) >> 40) & ~0xFFF) | ((int)(x) & 0xFFF))
>  #define put_pte_flags(x) (((intpte_t)((x) & ~0xFFF) << 40) | ((x) & 0xFFF))
>  
> +/*
> + * Protection keys define a new 4-bit protection key field
> + * (PKEY) in bits 62:59 of leaf entries of the page tables.
> + * This corresponds to bit 22:19 of a 24-bit flags.
> + *
> + * Notice: Bit 22 is used by _PAGE_GNTTAB which is visible to PV guests,
> + * so Protection keys must be disabled on PV guests.
> + */
> +#define _PAGE_PKEY_BIT0 (1u<<19)       /* Protection Keys, bit 1/4 */
> +#define _PAGE_PKEY_BIT1 (1u<<20)       /* Protection Keys, bit 2/4 */
> +#define _PAGE_PKEY_BIT2 (1u<<21)       /* Protection Keys, bit 3/4 */
> +#define _PAGE_PKEY_BIT3 (1u<<22)       /* Protection Keys, bit 4/4 */
> +
> +/* The order of mask _PAGE_PKEY_BIT0 is 19 */
> +#define get_pte_pkeys(x) ((int)(get_pte_flags(x) >> 19) & 0xF)
> +
> +/* Take pkey first bit as pkey feature */
> +#define _PAGE_PKEY_BIT _PAGE_PKEY_BIT0

You have not addressed Jan's feedback from v1.

~Andrew

  reply	other threads:[~2015-12-01 20:11 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 [this message]
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

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=565DFEEC.3060200@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.