From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kqemu processor feature question
Date: Wed, 19 Oct 2005 17:46:50 -0400 [thread overview]
Message-ID: <20051019214650.GA25061@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <43569A6F.7070002@wasp.net.au>
On Wed, Oct 19, 2005 at 11:11:43PM +0400, Brad Campbell wrote:
> It is off.. that is my issue.. Not quite sure what is going on ..
> Anyway.. the -no-tsc patch works around my issue, but there is still
> something wierd going on with
> my tsc.
>
> Regards,
> Brad
> --
> "Human beings, who are almost unique in having the ability
> to learn from the experience of others, are also remarkable
> for their apparent disinclination to do so." -- Douglas Adams
qemu uses an unreliable timesource, the rdtsc instruction. That works most of
the time but is not a good idea when CPU usage varies a lot. I'm not suprised
at the difference across cpus either.
I'm not sure if kqemu has an effect on this or not (but if it does, kernel code
would probably have slower ticks that user mode code).
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2005-10-19 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 5:10 [Qemu-devel] kqemu processor feature question Brad Campbell
2005-10-18 18:43 ` Francois Rioux
2005-10-18 20:34 ` Brad Campbell
2005-10-18 21:03 ` John R. Hogerhuis
2005-10-18 21:17 ` Brad Campbell
2005-10-19 6:18 ` [Qemu-devel] Timing.. was : " Brad Campbell
2005-10-19 23:09 ` Sven Zenker
2005-10-19 18:23 ` [Qemu-devel] " Emmanuel Pellereau
2005-10-19 19:11 ` Brad Campbell
2005-10-19 21:46 ` Jim C. Brown [this message]
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=20051019214650.GA25061@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--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).