From: "Hollis Blanchard" <hollis@penguinppc.org>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v3] powerpc: Unify opcode definitions and support
Date: Wed, 14 Jan 2009 13:51:42 -0600 [thread overview]
Message-ID: <fb412d760901141151g63d9e888o9437afe6f8e1313a@mail.gmail.com> (raw)
In-Reply-To: <1231884862-10693-1-git-send-email-galak@kernel.crashing.org>
On Tue, Jan 13, 2009 at 4:14 PM, Kumar Gala <galak@kernel.crashing.org> wrote:
> Create a new header that becomes a single location for defining PowerPC
> opcodes used by code that is either generationg instructions
> at runtime (fixups, debug, etc.), emulating instructions, or just
> compiling instructions old assemblers don't know about.
>
> We currently don't handle the floating point emulation or alignment decode
> as both are better handled by the specific decode support they already
> have.
>
> Added support for the new dcbzl, dcbal, msgsnd, tlbilx, & wait instructions
> since older assemblers don't know about them.
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> * Added PPC_ prefixes to everything to ensure namespace
> * removed defines from traps.c
>
> arch/powerpc/include/asm/code-patching.h | 4 +-
> arch/powerpc/include/asm/ppc-opcode.h | 68 ++++++++++++++++++++++++++++++
> arch/powerpc/include/asm/ppc_asm.h | 6 +--
> arch/powerpc/kernel/crash_dump.c | 2 +-
> arch/powerpc/kernel/entry_32.S | 8 ++--
> arch/powerpc/kernel/ftrace.c | 8 ++--
> arch/powerpc/kernel/head_booke.h | 2 +-
> arch/powerpc/kernel/module_64.c | 2 +-
> arch/powerpc/kernel/traps.c | 58 ++++++++-----------------
> arch/powerpc/lib/feature-fixups.c | 4 +-
> 10 files changed, 101 insertions(+), 61 deletions(-)
> create mode 100644 arch/powerpc/include/asm/ppc-opcode.h
Shouldn't arch/powerpc/include/asm/disassemble.h be integrated with this?
-Hollis
prev parent reply other threads:[~2009-01-14 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 22:14 [PATCH v3] powerpc: Unify opcode definitions and support Kumar Gala
2009-01-14 19:51 ` Hollis Blanchard [this message]
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=fb412d760901141151g63d9e888o9437afe6f8e1313a@mail.gmail.com \
--to=hollis@penguinppc.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).