qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Filip Navara <filip.navara@gmail.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ARM7TDMI emulation
Date: Tue, 16 Jun 2009 23:47:01 +0200	[thread overview]
Message-ID: <5b31733c0906161447q5bdb6f1bq3d7d3b07977df7be@mail.gmail.com> (raw)
In-Reply-To: <5b31733c0906161349l62255380rbd63647e7d9ee415@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]

On Tue, Jun 16, 2009 at 10:49 PM, Filip Navara <filip.navara@gmail.com>wrote:

> Do you know of a good summary reference which lists which instructions
>>  are available in each ARM architecture level from ARMv4 up to ARMv7
>> and it's variants?
>>
>
> My main reference are the technical reference manuals for ARM processors
> downloaded from Atmel site. I'm not sure about the license, but it states
> "This document is Open Access. This document has no restriction on
> distribution." Other reference sources are Skyeye emulation (has to be taken
> with grain of salt and checked against the manuals, but it makes distinction
> between v4, v5 and v5e) and Paul Brook.
>
> I've certainly missed handling BLX (at least on three places) in the patch
> and possibly more. I'll post an updated patch soon.
>

The list may not be complete, but this is what I compiled from various
sources, including ARM official documentation. For the ARMv4t emulation I'd
need to do the following:

- Treat CDP2, LDC2, STC2, BLX, MRC2, MCR2, MCRR, SMUL, SMLA, SMULW,
SMLAW, SMLAL, QADD, QSUB, QDADD, QDSUB, BKPT, 64-bit LDR/STR, PLD as
undefined instructions.
- Do not change to/from Thumb mode on LDR/LDM/POP to r15 depending on the
bit 0 of the value.
- Add the base updated data-abort model.

Other changes between ARMv5 and ARMv4 include:

- MULS, MLAS corrupt C flag
- UMULLS, UMLALS, SMULLS and SMLALS corrupt the C and V flags

I don't plan to implement corrupting the flags. Implementing ARMv4 instead
of ARMv4t would then be matter of disabling the BX instruction. Anything I
missed?

Best regards,
Filip Navara

[-- Attachment #2: Type: text/html, Size: 2320 bytes --]

  reply	other threads:[~2009-06-16 21:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-02 13:27 [Qemu-devel] [PATCH] ARM7TDMI emulation Ulrich Hecht
2007-07-02 13:40 ` Paul Brook
2007-07-02 16:14   ` Ulrich Hecht
2007-07-03 14:45     ` Ulrich Hecht
2009-06-15 19:11       ` Filip Navara
2009-06-16 17:25         ` Paul Brook
2009-06-16 19:02           ` Jamie Lokier
2009-06-16 19:05             ` Paul Brook
2009-06-16 20:49             ` Filip Navara
2009-06-16 21:47               ` Filip Navara [this message]
2009-06-17  9:55               ` Filip Navara
2009-06-17 10:24                 ` Filip Navara
  -- strict thread matches above, loose matches on Subject: below --
2009-07-15 12:08 Filip Navara

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=5b31733c0906161447q5bdb6f1bq3d7d3b07977df7be@mail.gmail.com \
    --to=filip.navara@gmail.com \
    --cc=jamie@shareable.org \
    --cc=paul@codesourcery.com \
    --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).