From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1F3s0n-0003Sq-Df
	for qemu-devel@nongnu.org; Tue, 31 Jan 2006 04:41:21 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1F3s0j-0003NH-Bn
	for qemu-devel@nongnu.org; Tue, 31 Jan 2006 04:41:19 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1F3s0h-0003LW-J0
	for qemu-devel@nongnu.org; Tue, 31 Jan 2006 04:41:16 -0500
Received: from [193.49.148.17] (helo=mail2.eseo.fr)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1F3rz9-0004lX-VP
	for qemu-devel@nongnu.org; Tue, 31 Jan 2006 04:39:40 -0500
Received: from harley.eseo.fr (harley.eseo.fr [192.168.11.1])
	by mail2.eseo.fr (Postfix) with ESMTP id 989A57ECD
	for <qemu-devel@nongnu.org>; Tue, 31 Jan 2006 10:30:29 +0100 (CET)
Received: from [192.168.10.220] (firewall.eseo.fr [192.168.11.49])
	by harley.eseo.fr (Postfix) with ESMTP id 9E9095D8B
	for <qemu-devel@nongnu.org>; Tue, 31 Jan 2006 10:38:06 +0100 (CET)
Message-ID: <43DF3039.6090604@eseo.fr>
Date: Tue, 31 Jan 2006 10:39:05 +0100
From: Jonathan ILIAS <jonathan.ilias@eseo.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: [Qemu-devel] changing simulated CPU frequency
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Hi,

I'm trying to bypass a bug in an old version of RTAI, which does not=20
work correctly with processors that have a clock greater than 2^31 Hz=20
(frequency stored in a signed 32 bits integer).

As I cannot use a earlier version and fixing this bug may not be=20
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=20
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=20
clock ?

I hope I've described my problem clearly...
--=20
Jonathan ILIAS, assistant p=E9dagogique
http://www.eseo.fr/~jilias/
ESEO
4, rue Merlet de la Boulaye
BP 30926 - 49009 ANGERS cedex 01 - FRANCE
t=E9l : 02 41 86 67 57