LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd.bergmann@de.ibm.com>
Subject: [PATCH 0/9] More xmon cell patches
Date: Wed, 22 Nov 2006 18:55:22 +1100	[thread overview]
Message-ID: <1164182122.302443.256192350213.qpush@cradle> (raw)

This is an updated series of xmon cell patches, it replaces the series
of three I sent earlier (Nov 3rd).

It fixes the xmon sparse warnings, updates 'ss, adds 'sd' and 'sdi'
commands to xmon - and incorporates updated disassembly code. Finally
we make the disassembly optional for folks looking for a smaller kernel.

The update of the ppc-dis.c code is RFC, I just thought I'd do it while I
was there. But I haven't tested it thoroughly.

cheers

             reply	other threads:[~2006-11-22  7:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22  7:55 Michael Ellerman [this message]
2006-11-22  7:55 ` [PATCH 1/9] Fix sparse warning in xmon Cell code Michael Ellerman
2006-11-22  7:55 ` [PATCH 2/9] Show state of spus as they're stopped in Cell xmon helper Michael Ellerman
2006-11-22  7:55 ` [PATCH 3/9] Add a 'sd' command (spu dump) to xmon to dump spu local store Michael Ellerman
2006-11-22  7:55 ` [PATCH 4/9] Prepare for spu disassembly in xmon Michael Ellerman
2006-11-22  7:55 ` [PATCH 5/9] Import spu disassembly code into xmon Michael Ellerman
2006-11-22  7:55 ` [PATCH 6/9] Add spu disassembly to xmon Michael Ellerman
2006-11-22  7:55 ` [PATCH 7/9] Make xmon disassembly optional Michael Ellerman
2006-11-22  7:55 ` [PATCH 8/9] Make 64-bit cpu features defined on 32-bit Michael Ellerman
2006-11-22  7:55 ` [PATCH 9/9] Import updated version of ppc disassembly code for xmon Michael Ellerman

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=1164182122.302443.256192350213.qpush@cradle \
    --to=michael@ellerman.id.au \
    --cc=arnd.bergmann@de.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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