From: "François Revol" <revol@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] [RFC] Make vmport report the processor speed
Date: Tue, 06 Jan 2009 05:24:07 +0100 CET [thread overview]
Message-ID: <24689573005-BeMail@laptop> (raw)
In-Reply-To: <1231171871-2320-2-git-send-email-agraf@suse.de>
> If VMware ESX finds itself virtualized (read: inside VMware),
> it reads the TSC speed
> from its backdoor, because measuring the TSC inside a VM is not
> exact.
>
> This patch implements a hacky way to detect the TSC speed and passes
> that through to
> the VM. I am open to suggestions on how to improve the behavior.
> It also adds a magic return value of 2 on the version return,
> which is required by
> VMware ESX.
Oh this is interesting, I might add some stuff to Haiku to use it.
BeOS (and Haiku) use RDTSC for timing, it's much more precise, but it's
why it runs so strange in VMs... (and will have to be handled when
implementing speedstep)
François.
next prev parent reply other threads:[~2009-01-06 4:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 16:11 [Qemu-devel] [PATCH 0/2] VMware ESX guest bringup (partial) Alexander Graf
2009-01-05 16:11 ` [Qemu-devel] [PATCH 1/2] [RFC] Make vmport report the processor speed Alexander Graf
2009-01-05 16:11 ` [Qemu-devel] [PATCH 2/2] Add phenom CPU descriptor Alexander Graf
2009-01-09 23:16 ` Alexander Graf
2009-01-09 23:36 ` Anthony Liguori
2009-01-05 16:37 ` [Qemu-devel] [PATCH 1/2] [RFC] Make vmport report the processor speed Anthony Liguori
2009-01-07 6:58 ` Alexander Graf
2009-01-06 4:24 ` François Revol [this message]
2009-01-06 4:56 ` Anthony Liguori
2009-01-06 22:33 ` Jamie Lokier
2009-01-07 6:29 ` Alexander Graf
2009-01-07 10:23 ` François Revol
2009-01-07 11:15 ` Alexander Graf
2009-01-07 11:32 ` François Revol
2009-01-07 14:34 ` Alexander Graf
2009-01-07 14:48 ` François Revol
2009-01-07 15:44 ` Alexander Graf
2009-01-07 16:46 ` Anthony Liguori
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=24689573005-BeMail@laptop \
--to=revol@free.fr \
--cc=qemu-devel@nongnu.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).