From: Jonathan ILIAS <jonathan.ilias@eseo.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] changing simulated CPU frequency
Date: Tue, 31 Jan 2006 10:39:05 +0100 [thread overview]
Message-ID: <43DF3039.6090604@eseo.fr> (raw)
Hi,
I'm trying to bypass a bug in an old version of RTAI, which does not
work correctly with processors that have a clock greater than 2^31 Hz
(frequency stored in a signed 32 bits integer).
As I cannot use a earlier version and fixing this bug may not be
trivial, I'm looking for a way to reduce the simulated Qemu CPU clock.
I tried to change linux-user/main.c to force the use of the following
version of cpu_get_real_ticks function :
static uint64_t emu_time;
int64_t cpu_get_real_ticks(void)
{
return emu_time++;
}
But Linux in Qemu continues to detect a CPU at 3,4 GHz.
Do you know if there is a way to modify Qemu source to have a lower CPU
clock ?
I hope I've described my problem clearly...
--
Jonathan ILIAS, assistant pédagogique
http://www.eseo.fr/~jilias/
ESEO
4, rue Merlet de la Boulaye
BP 30926 - 49009 ANGERS cedex 01 - FRANCE
tél : 02 41 86 67 57
reply other threads:[~2006-01-31 9:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43DF3039.6090604@eseo.fr \
--to=jonathan.ilias@eseo.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).