From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: emulated tsc and frequency info
Date: Tue, 20 Jul 2010 13:52:36 +0200 [thread overview]
Message-ID: <4C458E04.4070807@ts.fujitsu.com> (raw)
In-Reply-To: <C86B324F.1B0BD%keir.fraser@eu.citrix.com>
On 07/20/2010 12:00 PM, Keir Fraser wrote:
> On 20/07/2010 10:20, "Juergen Gross"<juergen.gross@ts.fujitsu.com> wrote:
>
>> with xen 4.0 and xen-unstable I see weird tsc information in my HVM-domain
>> with PV-driver, if xen chooses to emulate tsc (d->arch.vtsc is set):
correction: only xen 4.0 is affected!
xen-unstable does the scaling correctly.
>>
>> In the shared info page the tsc_to_system_mul is still reflecting the host
>> cpu frequency instead of the emulated 1 GHz.
>>
>> The reason is quite simple: tsc_set_info() is never called with a gtsc_khz
>> value other than 0. I wonder which solution is the correct one:
>> - if tsc_set_info() is called with gtsc_khz=0, assume 1 GHz (my favorite).
>
> That sounds best to me. Cc'ing Dan as he may have an opinion.
>
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2010-07-20 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 9:20 emulated tsc and frequency info Juergen Gross
2010-07-20 10:00 ` Keir Fraser
2010-07-20 11:52 ` Juergen Gross [this message]
2010-07-20 12:28 ` Keir Fraser
2010-07-20 12:43 ` Juergen Gross
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=4C458E04.4070807@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=dan.magenheimer@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).