From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] [RFC] Make vmport report the processor speed
Date: Tue, 6 Jan 2009 22:33:04 +0000 [thread overview]
Message-ID: <20090106223303.GC25563@shareable.org> (raw)
In-Reply-To: <1231171871-2320-2-git-send-email-agraf@suse.de>
Alexander Graf wrote:
> 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. WARNING: This
> implementation breaks on non-x86 hosts!
If you run _this_ code as a guest inside itself, shouldn't it _call_
VMPORT_CMD_GETPROCSPEED to get the value? :-)
-- Jamie
next prev parent reply other threads:[~2009-01-06 22:33 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
2009-01-06 4:56 ` Anthony Liguori
2009-01-06 22:33 ` Jamie Lokier [this message]
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=20090106223303.GC25563@shareable.org \
--to=jamie@shareable.org \
--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 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.