qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] SH: Add prefi, icbi, synco
Date: Mon, 20 Oct 2008 18:07:10 +0100	[thread overview]
Message-ID: <200810201807.11669.paul@codesourcery.com> (raw)
In-Reply-To: <20081020164913.GA24337@linux-sh.org>

> The issue comes with how the ISA is versioned. It changes across CPU
> families, with different families borrowing off of each other but not
> being strict supersets of previous generations. It is a complicated mess
> in binutils, and if someone has a better idea of how to do that cleanly
> in qemu, then that is certainly something that should be experimented
> with.

> In addition to the CPU subtype, it is necessary to track the CPU family
> that it falls under also, as this is the only way to know properly how
> the instructions have been inherited.

Binutils ends up a mess because it tries to create a hierarchal tree of cpus, 
IIRC because of the way it represents this in the object file. Qemu is quite 
happy to pick and choose features. There's no need to complicate things by 
pretending there's some sort of logic behind the ISA revisions.

> Going be a set of features is possible to some extent, but there are
> fundamental architectural differences in SH-4A compared to SH-4, so the
> feature thing is rather misleading.

ARM and PPC already have support for multiple system models.
I'd guess most of these differences aren't actually part of the CPU core, 
they're part of the supporting devices/peripherals.

Paul

  reply	other threads:[~2008-10-20 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 12:52 [Qemu-devel] [PATCH] SH: Add prefi, icbi, synco Vladimir Prus
2008-10-17 19:56 ` Paul Brook
2008-10-20  4:01   ` Paul Mundt
2008-10-20 10:54     ` Paul Brook
2008-10-20 13:00       ` Paul Mundt
2008-10-20 16:27         ` Paul Brook
2008-10-20 16:31           ` Vladimir Prus
2008-10-20 16:46             ` Paul Brook
2008-10-20 16:49             ` Paul Mundt
2008-10-20 17:07               ` Paul Brook [this message]
2008-10-20 17:15       ` Laurent Desnogues
2008-10-20 17:19         ` Paul Brook

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=200810201807.11669.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vladimir@codesourcery.com \
    /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).