From: Babu Moger <babu.moger@amd.com>
To: corbet@lwn.net, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, pbonzini@redhat.com,
sean.j.christopherson@intel.com
Cc: x86@kernel.org, vkuznets@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, mchehab+samsung@kernel.org,
babu.moger@amd.com, changbin.du@intel.com, namit@vmware.com,
bigeasy@linutronix.de, yang.shi@linux.alibaba.com,
asteinhauser@google.com, anshuman.khandual@arm.com,
jan.kiszka@siemens.com, akpm@linux-foundation.org,
steven.price@arm.com, rppt@linux.vnet.ibm.com, peterx@redhat.com,
dan.j.williams@intel.com, arjunroy@google.com,
logang@deltatee.com, thellstrom@vmware.com, aarcange@redhat.com,
justin.he@arm.com, robin.murphy@arm.com, ira.weiny@intel.com,
keescook@chromium.org, jgross@suse.com,
andrew.cooper3@citrix.com, pawan.kumar.gupta@linux.intel.com,
fenghua.yu@intel.com, vineela.tummalapalli@intel.com,
yamada.masahiro@socionext.com, sam@ravnborg.org, acme@redhat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: [PATCH v4 0/3] arch/x86: Enable MPK feature on AMD
Date: Tue, 12 May 2020 18:58:46 -0500 [thread overview]
Message-ID: <158932780954.44260.4292038705292213548.stgit@naples-babu.amd.com> (raw)
AMD's next generation of EPYC processors support the MPK (Memory
Protection Keys) feature.
This series enables the feature on AMD and updates config parameters
and documentation to reflect the MPK support on x86 platforms.
AMD documentation for MPK feature is available at "AMD64 Architecture
Programmer’s Manual Volume 2: System Programming, Pub. 24593 Rev. 3.34,
Section 5.6.6 Memory Protection Keys (MPK) Bit".
The documentation can be obtained at the link below:
https://bugzilla.kernel.org/show_bug.cgi?id=206537
---
v4:
- Removed all the source changes related to config parameter.
Just kept the doc changes and add new config parameter
X86_MEMORY_PROTECTION_KEYS which shadows X86_INTEL_MEMORY_PROTECTION_KEYS.
- Minor change in feature detection in kvm/cpuid.c
v3:
https://lore.kernel.org/lkml/158923982830.20128.14580309786525588408.stgit@naples-babu.amd.com/#r
- Fixed the problem Jim Mattson pointed out which can cause pkru
resources to get corrupted during host and guest switches.
- Moved the PKU feature detection code from VMX.c to common code.
v2:
https://lore.kernel.org/lkml/158897190718.22378.3974700869904223395.stgit@naples-babu.amd.com/
- Introduced intermediate config option X86_MEMORY_PROTECTION_KEYS to
avoid user propmpts. Kept X86_INTEL_MEMORY_PROTECTION_KEYS as is.
Eventually, we will be moving to X86_MEMORY_PROTECTION_KEYS after
couple of kernel revisions.
- Moved pkru data structures to kvm_vcpu_arch. Moved save/restore pkru
to kvm_load_host_xsave_state/kvm_load_guest_xsave_state.
v1:
https://lore.kernel.org/lkml/158880240546.11615.2219410169137148044.stgit@naples-babu.amd.com/
Babu Moger (3):
arch/x86: Update config and kernel doc for MPK feature on AMD
KVM: x86: Move pkru save/restore to x86.c
KVM: x86: Move MPK feature detection to common code
Documentation/core-api/protection-keys.rst | 3 ++-
arch/x86/Kconfig | 14 ++++++++++++--
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/cpuid.c | 9 ++++++++-
arch/x86/kvm/vmx/vmx.c | 22 ----------------------
arch/x86/kvm/x86.c | 17 +++++++++++++++++
6 files changed, 40 insertions(+), 26 deletions(-)
--
Signature
next reply other threads:[~2020-05-12 23:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 23:58 Babu Moger [this message]
2020-05-12 23:58 ` [PATCH v4 1/3] arch/x86: Update config and kernel doc for MPK feature on AMD Babu Moger
2020-05-13 15:09 ` Dave Hansen
2020-05-13 15:56 ` Babu Moger
2020-05-12 23:59 ` [PATCH v4 2/3] KVM: x86: Move pkru save/restore to x86.c Babu Moger
2020-05-12 23:59 ` [PATCH v4 3/3] KVM: x86: Move MPK feature detection to common code Babu Moger
2020-05-13 15:35 ` [PATCH v4 0/3] arch/x86: Enable MPK feature on AMD Paolo Bonzini
2020-05-13 16:00 ` Babu Moger
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=158932780954.44260.4292038705292213548.stgit@naples-babu.amd.com \
--to=babu.moger@amd.com \
--cc=aarcange@redhat.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=anshuman.khandual@arm.com \
--cc=arjunroy@google.com \
--cc=asteinhauser@google.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=changbin.du@intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=ira.weiny@intel.com \
--cc=jan.kiszka@siemens.com \
--cc=jgross@suse.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=justin.he@arm.com \
--cc=keescook@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=luto@kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mingo@redhat.com \
--cc=namit@vmware.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=sam@ravnborg.org \
--cc=sean.j.christopherson@intel.com \
--cc=steven.price@arm.com \
--cc=tglx@linutronix.de \
--cc=thellstrom@vmware.com \
--cc=vineela.tummalapalli@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
--cc=yang.shi@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).