qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] MIPS instruction set configuration
Date: Mon, 03 Jul 2006 10:32:21 +0200	[thread overview]
Message-ID: <44A8D615.9060004@bellard.org> (raw)
In-Reply-To: <20060702231636.GB18996@networkno.de>

Thiemo Seufer wrote:
> Dirk Behme wrote:
> 
>>Fabrice Bellard wrote:
>>
>>>You should add a runtime selection system : see the ARM and PowerPC 
>>>targets (I would prefer a parameter to cpu_init(). It was not done that 
>>>way on PowerPC for legacy reasons). Each machine should be able to 
>>>select the processor it needs (and allow the user to change it if 
>>>needed, but it is not the main point).
> 
> 
> It might be interesting for MIPS to decouple Machine and CPU somewhat.
> E.g. the Malta board supports a number of different 32- and 64-bit CPUs.

Each machine can add specific support for that (for example a -cpu 
option). It is likely to come at least for the PC machines.

>>>There is no good reason to make 
>>>the selection at compile time because the translator can efficiently 
>>>handle any CPU differences at runtime.
> 
> 
> I'm a bit dubious about this argument, each instruction needs to be
> checked agains a tuple of values. How much performance loss would be
> acceptable?

It slows down the translator a bit, but most of the time is spent in the 
generated code, not in the translator (otherwise there is no point in 
doing dynamic translation !).

>[...]
> Unfortunately it is not that simple. We have the upward-compatible ISAs:
 >[...]

I add suggest one more parameter to cpu_mips_set_model() to specify 
optional features. A function converting a CPU "string id" into an id + 
features would be interesting too.

Fabrice.

  reply	other threads:[~2006-07-03  8:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25 16:12 [Qemu-devel] Pending MIPS patches Dirk Behme
2006-06-25 16:39 ` Fabrice Bellard
2006-06-26  9:35   ` Marius Groeger
2006-06-26 15:35   ` Dirk Behme
2006-06-26 20:17     ` Fabrice Bellard
2006-06-27 15:45       ` MIPS instruction set configuration, was: " Dirk Behme
2006-06-27 15:55         ` [Qemu-devel] Re: MIPS instruction set configuration Marius Groeger
2006-06-27 20:57           ` Fabrice Bellard
2006-07-02 16:27             ` [Qemu-devel] [PATCH] " Dirk Behme
2006-07-02 23:16               ` Thiemo Seufer
2006-07-03  8:32                 ` Fabrice Bellard [this message]
2006-07-03  9:50                   ` Thiemo Seufer
2006-07-03 14:32                   ` Dirk Behme
2006-07-03 14:53                     ` Fabrice Bellard
2006-07-08  6:15                       ` Dirk Behme
2006-07-03 14:20                 ` Dirk Behme
2006-07-03 17:02                   ` Thiemo Seufer
2006-07-03 18:41                     ` Stefan Weil
2006-07-03 19:58                       ` Thiemo Seufer
2006-07-08  6:19                     ` Dirk Behme
2006-07-08 12:47                       ` Thiemo Seufer
     [not found]   ` <44A001C7.8040303@gmail.com>
2006-06-26 17:27     ` [Qemu-devel] Pending MIPS patches Raphaël Rigo
2006-06-27 21:08       ` Fabrice Bellard
2006-06-27 21:15       ` Fabrice Bellard

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=44A8D615.9060004@bellard.org \
    --to=fabrice@bellard.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 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).