From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FXihl-0001n0-G2
	for qemu-devel@nongnu.org; Sun, 23 Apr 2006 13:49:05 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FXihj-0001lH-5H
	for qemu-devel@nongnu.org; Sun, 23 Apr 2006 13:49:04 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FXihj-0001l9-19
	for qemu-devel@nongnu.org; Sun, 23 Apr 2006 13:49:03 -0400
Received: from [193.7.176.20] (helo=bender.bawue.de)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1FXijm-0003Iw-Ae
	for qemu-devel@nongnu.org; Sun, 23 Apr 2006 13:51:10 -0400
Date: Sun, 23 Apr 2006 18:48:47 +0100
Subject: Re: [Qemu-devel] new MIPS instructions
Message-ID: <20060423174847.GA9279@networkno.de>
References: <444BB919.3060403@bellard.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <444BB919.3060403@bellard.org>
From: Thiemo Seufer <ths@networkno.de>
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

Fabrice Bellard wrote:
> Hi,
> 
> Since many new MIPS instructions are added, I think it is very important 
>  now to add a way to dynamically select the exact MIPS processor model 
> that is emulated in QEMU.

FWIW, I added MIPS32R2 instructions to my local copy while keeping the
CPU a MIPS32R1 4k. This is enough to boot a R2 Linux kernel, and it
should also be good enough to run a R2 userland.

I used the generic architecture spec, currently without using a specific
implementation (the latter would be nice for watchpoints and performance
registers, which are implementation specific).

> I suggest adding a parameter to cpu_mips_init() telling the exact CPU 
> model which is emulated. Optionnal features (such as the FPU) could be 
> specified with an additionnal parameter.

Probably with an additional switch "emulate everything we know about",
which would be especially useful for usermode emulation where CPU
specifics don't matter that much.


Thiemo