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] cell: spu management xmon routines
Date: Wed, 22 Nov 2006 18:58:04 +1100 [thread overview]
Message-ID: <20061122075809.4C41467CAE@ozlabs.org> (raw)
In-Reply-To: <4563CFED.1020508@am.sony.com>
This fixes the xmon support for the cell spu to be compatable with the split
spu platform code.
Signed-off-by: Geoff Levand <geoffrey.levand@am.sony.com>
Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
---
Fixed to work on top of the changes I sent recently to fixup
sparse warnings in xmon.
---
arch/powerpc/xmon/xmon.c | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
Index: cell/arch/powerpc/xmon/xmon.c
===================================================================
--- cell.orig/arch/powerpc/xmon/xmon.c
+++ cell/arch/powerpc/xmon/xmon.c
@@ -2787,8 +2787,6 @@ static void dump_spu_fields(struct spu *
DUMP_FIELD(spu, "0x%x", number);
DUMP_FIELD(spu, "%s", name);
- DUMP_FIELD(spu, "%s", devnode->full_name);
- DUMP_FIELD(spu, "0x%x", nid);
DUMP_FIELD(spu, "0x%lx", local_store_phys);
DUMP_FIELD(spu, "0x%p", local_store);
DUMP_FIELD(spu, "0x%lx", ls_size);
@@ -2815,14 +2813,8 @@ static void dump_spu_fields(struct spu *
in_be32(&spu->problem->spu_status_R));
DUMP_VALUE("0x%x", problem->spu_npc_RW,
in_be32(&spu->problem->spu_npc_RW));
- DUMP_FIELD(spu, "0x%p", priv1);
-
- if (spu->priv1) {
- DUMP_VALUE("0x%lx", priv1->mfc_sr1_RW,
- in_be64(&spu->priv1->mfc_sr1_RW));
- }
-
DUMP_FIELD(spu, "0x%p", priv2);
+ DUMP_FIELD(spu, "0x%p", pdata);
}
int
prev parent reply other threads:[~2006-11-22 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 4:19 [PATCH 3/14] cell: spu management xmon routines Geoff Levand
2006-11-22 7:58 ` Michael Ellerman [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=20061122075809.4C41467CAE@ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).