From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Valtteri Kiviniemi <valtteri.kiviniemi@dataproof.fi>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Latest unstable detects cpu speed incorrectly
Date: Tue, 27 Oct 2009 16:05:58 +0000 [thread overview]
Message-ID: <C70CCAE6.188FD%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4AE716EC.5090508@dataproof.fi>
Haven't heard any other reports of that. Can you provide more details?
-- Keir
On 27/10/2009 15:51, "Valtteri Kiviniemi" <valtteri.kiviniemi@dataproof.fi>
wrote:
> Hi,
>
> Seems like that emulation is not quite working as it should be. domU's
> are using all the available cpu and then they crash. I did a fallback
> back to the old behaviour and the virtuals running with tsc_native=1 are
> working fine.
>
> - Valtteri Kiviniemi
>
> Valtteri Kiviniemi kirjoitti:
>> Hi,
>>
>> Ok, good to know. Is it always at 1GHz or can it be adjusted? Is there
>> some other new features different from 3.4.1 that I should know?
>>
>>
>> - Valtteri Kiviniemi
>>
>> Keir Fraser kirjoitti:
>>> On 27/10/2009 15:22, "Valtteri Kiviniemi"
>>> <valtteri.kiviniemi@dataproof.fi>
>>> wrote:
>>>
>>>> We are testing the latest xen-unstable and found an interesting bug.
>>>> dom0 detects cpu speed correctly but when booting domU it detects it
>>>> incorrectly:
>>>>
>>>> "Detected 1000.000 MHz processor."
>>>
>>> TSC is emulated at that speed. If you want old behaviour then add
>>> tsc_native=1
>>> to your domain config file.
>>>
>>> -- Keir
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-10-27 16:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 15:22 Latest unstable detects cpu speed incorrectly Valtteri Kiviniemi
2009-10-27 15:27 ` Pasi Kärkkäinen
2009-10-27 15:28 ` Keir Fraser
2009-10-27 15:48 ` Valtteri Kiviniemi
2009-10-27 15:51 ` Valtteri Kiviniemi
2009-10-27 16:05 ` Keir Fraser [this message]
2009-10-27 16:12 ` Valtteri Kiviniemi
2009-10-27 16:14 ` Valtteri Kiviniemi
2009-10-27 16:15 ` Valtteri Kiviniemi
2009-10-27 16:27 ` Keir Fraser
2009-10-27 16:32 ` Valtteri Kiviniemi
2009-10-27 16:34 ` Valtteri Kiviniemi
2009-10-27 16:36 ` Valtteri Kiviniemi
2009-10-27 19:46 ` Jeremy Fitzhardinge
2009-10-27 19:48 ` Jeremy Fitzhardinge
2009-10-27 21:39 ` Valtteri Kiviniemi
2009-10-27 21:40 ` Valtteri Kiviniemi
2009-10-27 16:47 ` Keir Fraser
2009-10-27 17:20 ` Mr. Teo En Ming (Zhang Enming)
2009-10-27 17:23 ` Keir Fraser
2009-10-27 17:25 ` Mr. Teo En Ming (Zhang Enming)
[not found] ` <C70CDFC0.18949%keir.fraser@eu.citrix.com>
2009-10-27 18:22 ` Mr. Teo En Ming (Zhang Enming)
2009-10-27 18:40 ` Keir Fraser
2009-10-27 18:47 ` Mr. Teo En Ming (Zhang Enming)
2009-10-27 18:56 ` Keir Fraser
2009-10-27 18:59 ` Mr. Teo En Ming (Zhang Enming)
2009-10-27 16:18 ` Mr. Teo En Ming (Zhang Enming)
2009-10-27 16:26 ` Mr. Teo En Ming (Zhang Enming)
2009-10-27 19:41 ` Jeremy Fitzhardinge
2009-10-27 16:02 ` Keir Fraser
2009-10-27 22:15 ` Dan Magenheimer
2009-10-27 22:31 ` Jeremy Fitzhardinge
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=C70CCAE6.188FD%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=valtteri.kiviniemi@dataproof.fi \
--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 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.