From: "Zhang, Haozhong" <haozhong.zhang@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH v2 2/2] x86/hvm: add support for pcommit instruction
Date: Tue, 5 Jan 2016 15:15:00 +0800 [thread overview]
Message-ID: <20160105071500.GA2440@hz-desktop.sh.intel.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F7644A6@SHSMSX101.ccr.corp.intel.com>
On 01/05/16 15:08, Tian, Kevin wrote:
> > From: Zhang, Haozhong
> > Sent: Wednesday, December 30, 2015 7:49 PM
> >
> > Pass PCOMMIT CPU feature into HMV domain. Currently, we do not intercept
> > pcommit instruction for L1 guest, and allow L1 to intercept pcommit
> > instruction for L2 guest.
>
> Could you elaborate why different policies are used for L1/L2? And better
> add a comment in code (at least for vvmx) to describe the intention.
>
> Thanks
> Kevin
The intention is that we completely expose pcommit (both the
instruction and VMEXIT caused by pcommit) to L1.
Haozhong
next prev parent reply other threads:[~2016-01-05 7:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 11:48 [PATCH v2 0/2] add support for vNVDIMM - Part 1: enable instructions Haozhong Zhang
2015-12-30 11:48 ` [PATCH v2 1/2] x86/hvm: allow guest to use clflushopt and clwb Haozhong Zhang
2015-12-30 11:53 ` Andrew Cooper
2016-01-05 7:02 ` Tian, Kevin
2016-01-07 13:49 ` Jan Beulich
2016-01-07 14:01 ` Andrew Cooper
2016-01-07 14:34 ` Jan Beulich
2016-01-08 8:27 ` Haozhong Zhang
2016-01-08 8:39 ` Jan Beulich
2015-12-30 11:48 ` [PATCH v2 2/2] x86/hvm: add support for pcommit instruction Haozhong Zhang
2015-12-30 11:57 ` Andrew Cooper
2016-01-05 7:08 ` Tian, Kevin
2016-01-05 7:15 ` Zhang, Haozhong [this message]
2016-01-05 7:19 ` Tian, Kevin
2016-01-05 7:32 ` Zhang, Haozhong
2016-01-05 7:45 ` Tian, Kevin
2016-01-07 13:53 ` Jan Beulich
2016-01-08 1:15 ` Haozhong Zhang
2016-01-08 7:54 ` Jan Beulich
2016-01-08 7:58 ` Haozhong Zhang
2016-01-04 11:10 ` [PATCH v2 0/2] add support for vNVDIMM - Part 1: enable instructions Wei Liu
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=20160105071500.GA2440@hz-desktop.sh.intel.com \
--to=haozhong.zhang@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.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 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.