From: Geoff Levand <geoffrey.levand@am•sony.com>
To: Michael Ellerman <michael@ellerman•id.au>
Cc: linuxppc-dev@ozlabs•org, Arnd Bergmann <arnd.bergmann@de•ibm.com>,
cbe-oss-dev@ozlabs•org
Subject: Re: [Cbe-oss-dev] [PATCH 2/2] Add support for dumping spu info from xmon
Date: Thu, 12 Oct 2006 10:42:38 -0700 [thread overview]
Message-ID: <452E7E8E.8000808@am.sony.com> (raw)
In-Reply-To: <20061012120312.10FDD67BE5@ozlabs.org>
Michael Ellerman wrote:
> This patch adds a command to xmon for dumping information about
> spu structs. The command is 'sf' for "spu fields" perhaps, and
> takes the spu number as an argument. This is the same value as the
> spu->number field, or the "phys-id" value of a context when it is
> bound to a physical spu.
> +static void dump_spu_fields(struct spu *spu)
> +{
...
> + DUMP_FIELD(spu, "0x%x", problem->spu_npc_RW);
> + DUMP_FIELD(spu, "0x%p", priv1);
> +
> + if (spu->priv1)
> + DUMP_FIELD(spu, "0x%lx", priv1->mfc_sr1_RW);
> +
> + DUMP_FIELD(spu, "0x%p", priv2);
Just to let you know, I've been doing some work to abstract the platform
specific parts out of the spu support to better support running on a
hypervisor. It shouldn't make much difference, but maybe I'll try to set
something up like this for you:
DUMP_FIELD(spu, "0x%x", problem->spu_npc_RW);
DUMP_FIELD(spu, "0x%p", priv2);
spu_dump_platform_fields(spu);
-Geoff
next prev parent reply other threads:[~2006-10-12 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 12:03 [PATCH 0/2] Cell xmon helpers Michael Ellerman
2006-10-12 12:03 ` [PATCH 1/2] Add support for stopping spus from xmon Michael Ellerman
2006-10-12 16:18 ` Linas Vepstas
2006-10-18 7:13 ` Michael Ellerman
2006-10-13 3:10 ` Haren Myneni
2006-10-18 7:16 ` Michael Ellerman
2006-10-13 3:18 ` Luke Browning
2006-10-18 7:14 ` Michael Ellerman
2006-10-12 12:03 ` [PATCH 2/2] Add support for dumping spu info " Michael Ellerman
2006-10-12 17:42 ` Geoff Levand [this message]
2006-10-18 6:56 ` [Cbe-oss-dev] " Michael Ellerman
2006-11-10 9:11 ` Geoff Levand
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=452E7E8E.8000808@am.sony.com \
--to=geoffrey.levand@am$(echo .)sony.com \
--cc=arnd.bergmann@de$(echo .)ibm.com \
--cc=cbe-oss-dev@ozlabs$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=michael@ellerman$(echo .)id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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