From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, eddie.dong@intel.com,
jun.nakajima@intel.com, suravee.suthikulpanit@amd.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH v4 1/3] x86: Use native RDTSC(P) execution when guest and host frequencies are the same
Date: Wed, 16 Apr 2014 11:33:16 -0400 [thread overview]
Message-ID: <534EA2BC.4050000@oracle.com> (raw)
In-Reply-To: <534EB1D502000078000099A9@nat28.tlf.novell.com>
On 04/16/2014 10:37 AM, Jan Beulich wrote:
>>>> On 16.04.14 at 16:28, <boris.ostrovsky@oracle.com> wrote:
>> On 04/16/2014 07:38 AM, Jan Beulich wrote:
>>>>>> On 16.04.14 at 03:27, <boris.ostrovsky@oracle.com> wrote:
>>>> @@ -1889,10 +1890,14 @@ void tsc_set_info(struct domain *d,
>>>> d->arch.vtsc_offset = get_s_time() - elapsed_nsec;
>>>> d->arch.tsc_khz = gtsc_khz ? gtsc_khz : cpu_khz;
>>>> set_time_scale(&d->arch.vtsc_to_ns, d->arch.tsc_khz * 1000 );
>>>> - /* use native TSC if initial host has safe TSC, has not migrated
>>>> - * yet and tsc_khz == cpu_khz */
>>>> - if ( host_tsc_is_safe() && incarnation == 0 &&
>>>> - d->arch.tsc_khz == cpu_khz )
>>>> + /*
>>>> + * Use native TSC if initial host has safe TSC and either has not
>>>> + * migrated yet or tsc_khz == cpu_khz (either "naturally" or via
>>>> + * TSC scaling)
>>>> + */
>>>> + if ( host_tsc_is_safe() &&
>>>> + (incarnation == 0 || d->arch.tsc_khz == cpu_khz ||
>>>> + cpu_has_tsc_ratio) )
>>> Doesn't this cpu_has_tsc_ratio check also need to be qualified with
>>> is_pv_domain()? And is the change from && in the old condition to ||
>>> actually valid for PV guests?
>> Hmm, I haven't thought about PV here.
>>
>> So then the condition should be
>>
>> if ( host_tsc_is_safe() )
>> {
>> if ( (is_hvm_domain() && (arch.tsc_khz == cpu_khz || cpu_has_tsc_ratio)) ||
>> (incarnation == 0 && d->arch.tsc_khz == cpu_khz) )
>> d->arch.vtsc = 0;
>> }
> Almost - to include PVH you need to either use !is_pv_domain() or
> has_hvm_container_domain().
PVH never makes here, it is forced to use TSC_MODE_NEVER_EMULATE above
(see pvhfixme above).
PVH need to be looked at anyway. For example, there is a is_hvm_domain()
check at the bottom which I suspect needs to be PVH-safe. I think it
should be addressed separately though.
-boris
next prev parent reply other threads:[~2014-04-16 15:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 1:27 [PATCH v4 0/3] Time-related fixes for migration Boris Ostrovsky
2014-04-16 1:27 ` [PATCH v4 1/3] x86: Use native RDTSC(P) execution when guest and host frequencies are the same Boris Ostrovsky
2014-04-16 9:54 ` Jan Beulich
2014-04-16 13:02 ` Boris Ostrovsky
2014-04-16 11:38 ` Jan Beulich
2014-04-16 14:28 ` Boris Ostrovsky
2014-04-16 14:37 ` Jan Beulich
2014-04-16 15:33 ` Boris Ostrovsky [this message]
2014-04-16 16:15 ` Jan Beulich
2014-04-16 16:44 ` Boris Ostrovsky
2014-04-17 6:29 ` Jan Beulich
2014-04-16 1:27 ` [PATCH v4 2/3] x86/svn: Enable TSC scaling Boris Ostrovsky
2014-04-16 10:21 ` Jan Beulich
2014-04-16 10:53 ` Andrew Cooper
2014-04-16 1:27 ` [PATCH v4 3/3] x86/HVM: Use fixed TSC value when saving or restoring domain Boris Ostrovsky
2014-04-16 10:22 ` 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=534EA2BC.4050000@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--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).