From: "Zhang, Haozhong" <haozhong.zhang@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v5 6/6] docs: Add descriptions of TSC scaling in xl.cfg and tscmode.txt
Date: Fri, 26 Feb 2016 12:44:31 +0800 [thread overview]
Message-ID: <20160226044431.GD13897@hz-desktop.sh.intel.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F7D293C@SHSMSX101.ccr.corp.intel.com>
On 02/26/16 12:37, Tian, Kevin wrote:
> > From: Zhang, Haozhong
> > Sent: Tuesday, February 23, 2016 10:05 AM
> >
> > Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>, except:
>
> > +
> > +Hardware TSC Scaling
> > +
> > +Intel VMX TSC scaling and AMD SVM TSC ratio allow the guest TSC read
> > +by guest rdtsc/p increasing in a different frequency than the host
> > +TSC frequency.
> > +
> > +If a HVM container in default TSC mode (tsc_mode=0) or PVRDTSCP mode
>
> 'HVM container' means something different. We usually use "HVM domain"
> as you may see in other places in this doc.
>
I'll change to 'HVM domain'.
Thanks,
Haozhong
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-26 4:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 2:04 [PATCH v5 0/6] Add VMX TSC scaling support Haozhong Zhang
2016-02-23 2:04 ` [PATCH v5 1/6] x86/hvm: Collect information of TSC scaling ratio Haozhong Zhang
2016-02-23 14:00 ` Boris Ostrovsky
2016-02-23 14:10 ` Jan Beulich
2016-02-23 14:16 ` Boris Ostrovsky
2016-02-23 15:37 ` Jan Beulich
2016-02-24 6:00 ` Haozhong Zhang
2016-02-24 13:46 ` Haozhong Zhang
2016-02-24 14:49 ` Boris Ostrovsky
2016-02-24 14:36 ` Jan Beulich
2016-02-24 15:03 ` Haozhong Zhang
2016-02-26 4:27 ` Tian, Kevin
2016-02-23 2:05 ` [PATCH v5 2/6] x86/hvm: Setup " Haozhong Zhang
2016-02-24 15:01 ` Jan Beulich
2016-02-24 15:42 ` Haozhong Zhang
2016-02-24 15:51 ` Jan Beulich
2016-02-24 16:05 ` Haozhong Zhang
2016-02-23 2:05 ` [PATCH v5 3/6] x86/hvm: Replace architecture TSC scaling by a common function Haozhong Zhang
2016-02-24 15:07 ` Jan Beulich
2016-02-26 4:30 ` Tian, Kevin
2016-02-23 2:05 ` [PATCH v5 4/6] x86/hvm: Move saving/loading vcpu's TSC to common code Haozhong Zhang
2016-02-23 2:05 ` [PATCH v5 5/6] vmx: Add VMX RDTSC(P) scaling support Haozhong Zhang
2016-02-24 15:09 ` Jan Beulich
2016-02-26 4:31 ` Tian, Kevin
2016-02-23 2:05 ` [PATCH v5 6/6] docs: Add descriptions of TSC scaling in xl.cfg and tscmode.txt Haozhong Zhang
2016-02-26 4:37 ` Tian, Kevin
2016-02-26 4:44 ` Zhang, Haozhong [this message]
2016-02-26 8:01 ` Jan Beulich
2016-02-26 8:05 ` Haozhong Zhang
2016-02-29 2:02 ` Tian, Kevin
2016-02-29 2:45 ` Zhang, Haozhong
2016-02-29 9:04 ` 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=20160226044431.GD13897@hz-desktop.sh.intel.com \
--to=haozhong.zhang@intel.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=suravee.suthikulpanit@amd.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).