From: Haozhong Zhang <haozhong.zhang@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Jun Nakajima <jun.nakajima@intel.com>,
Keir Fraser <keir@xen.org>
Subject: Re: [PATCH XEN v3 0/2] add support for vNVDIMM - Part 1: enable instructions
Date: Fri, 8 Jan 2016 21:03:17 +0800 [thread overview]
Message-ID: <20160108130317.GA16393@hz-desktop.sh.intel.com> (raw)
In-Reply-To: <568FB09E02000078000C4D39@prv-mh.provo.novell.com>
On 01/08/16 04:50, Jan Beulich wrote:
> >>> On 08.01.16 at 11:46, <haozhong.zhang@intel.com> wrote:
> > I split the previous patch series "[PATCH 0/4] add support for vNVDIMM"
> > into two parts. This is the first part that enables clflushopt/clwb/pcommit
> > instructions for HVM guests.
> >
> > Changes in v3:
> > * Remove unnecessary hypervisor code for clflushopt and clwb in patch 1.
>
> Which should have led to a Cc list reduction.
>
I'll take care in the next time.
> > * Move the code refactoring in hvm_cpuid() to patch 2.
> > * Replace checking host cpuid by checking VMX capabilities for pcommit.
>
> Replace?
>
Yes, akin to how MPX is checked in hvm_cpuid(). Or do you mean it's
better to check host cpuid as well?
Haozhong
next prev parent reply other threads:[~2016-01-08 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 10:46 [PATCH XEN v3 0/2] add support for vNVDIMM - Part 1: enable instructions Haozhong Zhang
2016-01-08 10:46 ` [PATCH XEN v3 1/2] x86/hvm: allow guest to use clflushopt and clwb Haozhong Zhang
2016-01-08 10:46 ` [PATCH XEN v3 2/2] x86/hvm: add support for pcommit instruction Haozhong Zhang
2016-01-08 11:50 ` [PATCH XEN v3 0/2] add support for vNVDIMM - Part 1: enable instructions Jan Beulich
2016-01-08 13:03 ` Haozhong Zhang [this message]
2016-01-08 13:41 ` Jan Beulich
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=20160108130317.GA16393@hz-desktop.sh.intel.com \
--to=haozhong.zhang@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.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 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).