From: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: H Peter Anvin <h.peter.anvin@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
"Kani, Toshimitsu" <toshi.kani@hp.com>,
"Knippers, Linda" <linda.knippers@hp.com>
Subject: RE: [PATCH v3 1/2] x86: Add support for the pcommit instruction
Date: Wed, 28 Jan 2015 17:10:46 +0000 [thread overview]
Message-ID: <94D0CD8314A33A4D9D801C0FE68B40295A75C517@G9W0745.americas.hpqcorp.net> (raw)
In-Reply-To: <1422377631-8986-2-git-send-email-ross.zwisler@linux.intel.com>
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of Ross Zwisler
> Sent: Tuesday, 27 January, 2015 10:54 AM
> To: linux-kernel@vger.kernel.org
> Cc: Ross Zwisler; H Peter Anvin; Ingo Molnar; Thomas Gleixner; Borislav
> Petkov
> Subject: [PATCH v3 1/2] x86: Add support for the pcommit instruction
>
> Add support for the new pcommit (persistent commit) instruction. This
> instruction was announced in the document "Intel Architecture
> Instruction Set Extensions Programming Reference" with reference number
> 319433-022.
>
> https://software.intel.com/sites/default/files/managed/0d/53/319433-
> 022.pdf
>
...
> ---
> arch/x86/include/asm/cpufeature.h | 1 +
> arch/x86/include/asm/special_insns.h | 8 ++++++++
> 2 files changed, 9 insertions(+)
Should this patch series also add defines for the virtual
machine control data structure changes?
1. Add the new VM-Execution Controls bit 21 as
SECONDARY_EXEC_PCOMMIT_EXITING 0x00200000
to arch/x86/include/asm/vmx.h.
2. Add the new exit reason of 64 (0x41) as
EXIT_REASON_PCOMMIT 64
to arch/x86/include/uapi/asm/vmx.h and (with a
VMX_EXIT_REASONS string) to usr/include/asm/vmx.h.
3. Add a kvm_vmx_exit_handler to arch/x86/kvm/vmx.c.
---
Rob Elliott HP Server Storage
next prev parent reply other threads:[~2015-01-29 2:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 16:53 [PATCH v3 0/2] add support for new persistent memory instructions Ross Zwisler
2015-01-27 16:53 ` [PATCH v3 1/2] x86: Add support for the pcommit instruction Ross Zwisler
2015-01-28 10:58 ` Borislav Petkov
2015-01-28 17:10 ` Elliott, Robert (Server Storage) [this message]
2015-01-28 17:21 ` Borislav Petkov
2015-01-28 17:27 ` Ross Zwisler
2015-02-11 22:24 ` H. Peter Anvin
2015-02-19 0:29 ` [tip:x86/asm] " tip-bot for Ross Zwisler
2015-02-19 1:15 ` Ingo Molnar
2015-02-19 17:21 ` Ross Zwisler
2015-02-19 17:33 ` Borislav Petkov
2015-02-19 17:41 ` Ross Zwisler
2015-01-27 16:53 ` [PATCH v3 2/2] x86: Add support for the clwb instruction Ross Zwisler
2015-01-28 10:58 ` Borislav Petkov
2015-02-11 22:25 ` H. Peter Anvin
2015-02-19 0:29 ` [tip:x86/asm] " tip-bot for Ross Zwisler
2015-04-02 20:31 ` Ross Zwisler
2015-04-03 5:04 ` Ingo Molnar
2015-04-03 5:10 ` [tip:x86/asm] x86/asm: Add support for the CLWB instruction tip-bot for Ross Zwisler
2015-02-05 16:24 ` [PATCH v3 0/2] add support for new persistent memory instructions Ross Zwisler
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=94D0CD8314A33A4D9D801C0FE68B40295A75C517@G9W0745.americas.hpqcorp.net \
--to=elliott@hp.com \
--cc=bp@alien8.de \
--cc=h.peter.anvin@intel.com \
--cc=linda.knippers@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.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).