From: Paolo Bonzini <pbonzini@redhat.com>
To: Huaitong Han <huaitong.han@intel.com>, gleb@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v3 0/7] KVM, pkeys: add memory protection-key support
Date: Wed, 18 Nov 2015 12:01:47 +0100 [thread overview]
Message-ID: <564C5A9B.9000407@redhat.com> (raw)
In-Reply-To: <1447825444-13550-1-git-send-email-huaitong.han@intel.com>
On 18/11/2015 06:43, Huaitong Han wrote:
> Changes in v3:
> *Add comments for patch that disable PKU feature without ept.
>
> Changes in v2:
> *Add pku.c for kvm-unit-tests.
> *Optimize permission_fault codes for patch4.
> *Delete is_long_mode and PK for patch5.
> *Squash cpuid and cr4 patches.
>
> The protection-key feature provides an additional mechanism by which IA-32e
> paging controls access to usermode addresses.
>
> Hardware support for protection keys for user pages is enumerated with CPUID
> feature flag CPUID.7.0.ECX[3]:PKU. Software support is CPUID.7.0.ECX[4]:OSPKE
> with the setting of CR4.PKE(bit 22).
>
> When CR4.PKE = 1, every linear address is associated with the 4-bit protection
> key located in bits 62:59 of the paging-structure entry that mapped the page
> containing the linear address. The PKRU register determines, for each
> protection key, whether user-mode addresses with that protection key may be
> read or written.
>
> The PKRU register (protection key rights for user pages) is a 32-bit register
> with the following format: for each i (0 ≤ i ≤ 15), PKRU[2i] is the
> access-disable bit for protection key i (ADi); PKRU[2i+1] is the write-disable
> bit for protection key i (WDi).
>
> Software can use the RDPKRU and WRPKRU instructions with ECX = 0 to read and
> write PKRU. In addition, the PKRU register is XSAVE-managed state and can thus
> be read and written by instructions in the XSAVE feature set.
>
> PFEC.PK (bit 5) is defined as protection key violations.
>
> The specification of Protection Keys can be found at SDM (4.6.2, volume 3)
> http://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-software-developer-manual-325462.pdf.
>
> The kernel native patchset have not yet been merged to upstream, you can found
> at git://git.kernel.org/pub/scm/linux/kernel/git/daveh/x86-pkeys.git pkeys-v007.
>
> Huaitong Han (7):
> KVM, pkeys: expose CPUID/CR4 to guest
> KVM, pkeys: disable pkeys for guests in non-paging mode
> KVM, pkeys: update memeory permission bitmask for pkeys
> KVM, pkeys: add pkeys support for permission_fault logic
> KVM, pkeys: Add pkeys support for gva_to_gpa funcions
> KVM, pkeys: add pkeys support for xsave state
> KVM, pkeys: disable PKU feature without ept
>
> arch/x86/include/asm/kvm_host.h | 11 +++++---
> arch/x86/kvm/cpuid.c | 24 ++++++++++++++++--
> arch/x86/kvm/cpuid.h | 8 ++++++
> arch/x86/kvm/mmu.c | 32 +++++++++++++++++++++--
> arch/x86/kvm/mmu.h | 56 +++++++++++++++++++++++++++++++++++++----
> arch/x86/kvm/paging_tmpl.h | 18 ++++++++++---
> arch/x86/kvm/vmx.c | 10 ++++----
> arch/x86/kvm/x86.c | 27 ++++++++++++++------
> arch/x86/kvm/x86.h | 3 ++-
> 9 files changed, 161 insertions(+), 28 deletions(-)
>
Looks good, but it will have to wait for kernel PKU support.
Thanks,
Paolo
prev parent reply other threads:[~2015-11-18 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 5:43 [PATCH v3 0/7] KVM, pkeys: add memory protection-key support Huaitong Han
2015-11-18 5:43 ` [PATCH v3 1/7] KVM, pkeys: expose CPUID/CR4 to guest Huaitong Han
2015-11-18 5:43 ` [PATCH v3 2/7] KVM, pkeys: disable pkeys for guests in non-paging mode Huaitong Han
2015-11-18 5:44 ` [PATCH v3 3/7] KVM, pkeys: update memeory permission bitmask for pkeys Huaitong Han
2015-11-18 5:44 ` [PATCH v3 4/7] KVM, pkeys: add pkeys support for permission_fault logic Huaitong Han
2015-11-18 5:44 ` [PATCH v3 5/7] KVM, pkeys: Add pkeys support for gva_to_gpa funcions Huaitong Han
2015-11-18 5:44 ` [PATCH v3 6/7] KVM, pkeys: add pkeys support for xsave state Huaitong Han
2015-11-18 5:44 ` [PATCH v3 7/7] KVM, pkeys: disable PKU feature without ept Huaitong Han
2015-11-18 9:06 ` Paolo Bonzini
2015-11-18 9:58 ` Han, Huaitong
2015-11-18 11:01 ` Paolo Bonzini [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=564C5A9B.9000407@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=huaitong.han@intel.com \
--cc=kvm@vger.kernel.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.