From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
Haozhong Zhang <haozhong.zhang@intel.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xen.org,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH v6 1/5] x86/hvm: Setup TSC scaling ratio
Date: Mon, 29 Feb 2016 08:49:11 -0500 [thread overview]
Message-ID: <56D44C57.9070805@oracle.com> (raw)
In-Reply-To: <56D458AC02000078000D7571@prv-mh.provo.novell.com>
On 02/29/2016 08:41 AM, Jan Beulich wrote:
>>>> On 28.02.16 at 13:54, <haozhong.zhang@intel.com> wrote:
>> This patch adds a field tsc_scaling_ratio in struct hvm_domain to record
>> the per-domain TSC scaling ratio, and sets it in tsc_set_info().
>>
>> Before setting the per-domain TSC scaling ratio, we check its validity
>> in tsc_set_info(). If an invalid ratio is given, we will leave the
>> default value in tsc_scaling_ratio (i.e. ratio = 1) and setup guest TSC
>> as if no TSC scaling is used:
>> * For TSC_MODE_FAULT,
s/TSC_MODE_FAULT/TSC_MODE_DEFAULT/
-boris
>> - if a user-specified TSC frequency is given, we will set the guest
>> TSC frequency to it; otherwise, we set it to the host TSC frequency.
>> - if guest TSC frequency does not equal to host TSC frequency, we will
>> emulate guest TSC (i.e. d->arch.vtsc is set to 1). In both cases,
>> guest TSC runs in the guest TSC frequency.
>> * For TSC_MODE_PVRDTSCP,
>> - we set the guest TSC frequency to the host TSC frequency.
>> - guest rdtsc is executed natively in the host TSC frequency as
>> before.
>> - if rdtscp is not available to guest, it will be emulated; otherwise,
>> it will be executed natively. In both cases, guest rdtscp gets TSC
>> in the host TSC frequency as before.
>>
>> Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-29 13:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 12:54 [PATCH v6 0/5] Add VMX TSC scaling support Haozhong Zhang
2016-02-28 12:54 ` [PATCH v6 1/5] x86/hvm: Setup TSC scaling ratio Haozhong Zhang
2016-02-29 13:41 ` Jan Beulich
2016-02-29 13:49 ` Boris Ostrovsky [this message]
2016-02-29 13:55 ` Haozhong Zhang
2016-02-29 13:55 ` Jan Beulich
2016-02-29 14:09 ` Boris Ostrovsky
2016-02-28 12:54 ` [PATCH v6 2/5] x86/hvm: Replace architecture TSC scaling by a common function Haozhong Zhang
2016-02-29 13:44 ` Jan Beulich
2016-02-29 14:03 ` Haozhong Zhang
2016-02-29 14:21 ` Boris Ostrovsky
2016-03-01 1:39 ` [PATCH v7 " Haozhong Zhang
2016-03-01 10:13 ` Jan Beulich
2016-02-28 12:54 ` [PATCH v6 3/5] x86/hvm: Move saving/loading vcpu's TSC to common code Haozhong Zhang
2016-02-28 12:54 ` [PATCH v6 4/5] vmx: Add VMX RDTSC(P) scaling support Haozhong Zhang
2016-02-28 12:54 ` [PATCH v6 5/5] docs: Add descriptions of TSC scaling in xl.cfg and tscmode.txt Haozhong Zhang
2016-03-01 14:09 ` Ian Jackson
2016-03-01 14:21 ` 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=56D44C57.9070805@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=haozhong.zhang@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).