From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: Add generic instruction opcode manipulation helpers
Date: Fri, 25 Nov 2011 11:32:54 +0000 [thread overview]
Message-ID: <20111125113254.GC2098@localhost.localdomain> (raw)
In-Reply-To: <1322220493-3251-1-git-send-email-dave.martin@linaro.org>
On Fri, Nov 25, 2011 at 11:28:13AM +0000, Dave Martin wrote:
> This patch adds some endianness-agnostic helpers to convert machine
> instructions between canonical integer form and in-memory
> representation, and also provides a transparent way to read a
> single Thumb instruction from memory, without the need to know the
> size in advance or write explicit condition checks.
>
> A canonical integer form for representing instructions is also
> formalised here.
>
> Signed-off-by: Dave Martin <dave.martin@linaro.org>
> ---
Notes:
* We don't necessarily need everything that's in this example header
* A generic instruction writing macro could be added, similar to the
generic read macro, if this looks useful.
* We could align the use of undefined instruction encodings across
the kernel via this header: all instruction sets allow a
guaranteed undefined instruction with up to 8 choosable bits,
and we can also define additional generic and "NULL" encodings
for internal use by kernel code which deals with instruction
opcodes -- to signal special cases and error values etc.
next prev parent reply other threads:[~2011-11-25 11:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 11:28 [RFC PATCH] ARM: Add generic instruction opcode manipulation helpers Dave Martin
2011-11-25 11:32 ` Dave Martin [this message]
2011-11-28 16:59 ` Rabin Vincent
2011-11-28 17:41 ` Dave Martin
2011-11-28 19:20 ` Tixy
2011-11-29 10:42 ` Dave Martin
2011-11-29 14:06 ` Jon Medhurst (Tixy)
2011-11-29 15:27 ` Dave Martin
2011-12-01 17:26 ` Rabin Vincent
2011-12-01 17:59 ` Dave Martin
2011-12-06 15:08 ` Will Deacon
2011-12-06 15:20 ` Dave Martin
2011-12-07 5:22 ` Bi Junxiao
2011-12-07 10:42 ` Dave Martin
2011-12-06 16:23 ` Jon Medhurst (Tixy)
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=20111125113254.GC2098@localhost.localdomain \
--to=dave.martin@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).