From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: mark.kettenis@xs4all.nl (Mark Kettenis), gdb-patches@sourceware.org
Subject: Re: [RFA][3/5] New port: Cell BE SPU (the port itself)
Date: Mon, 13 Nov 2006 12:27:00 -0000 [thread overview]
Message-ID: <200611131227.kADCRe28032402@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20061112221146.GA24918@nevyn.them.org> from "Daniel Jacobowitz" at Nov 12, 2006 05:11:46 PM
Daniel Jacobowitz wrote:
> On Sun, Nov 12, 2006 at 10:41:34PM +0100, Mark Kettenis wrote:
> > I think that what you really want is a Linux powerpc native configuration
> > that can debug both normal powerpc code and spu code. That'd mean adding
> > spu-linux-nat.c to config/powerpc/linux.mh. But I suppose that doesn't
> > really work right now. But could we make that work?
>
> In theory yes - but I'm not quite sure how. You'd have more than one
> target that could take control when you said "run" and for Cell I think
> you'd have to disambiguate based on the architecture of the file. But
> Ulrich said they had more patches that weren't ready for mainline and I
> bet some of them make this nicer :-) Since really you would want to
> debug both at once.
Yes, exactly. It's not just a matter of checking the executable file
architecture; a single process can have threads executing SPU code at
the same as other threads executing PowerPC code.
I have a set of patches that does appear to work so far; it is based
primarily on switching current_gdbarch on thread switch. However,
there's still some work to be done before this is in a shape suitable
for mainline inclusion.
Therefore I'd hoped it would be possible to get the SPU-only port
accepted first, since this is in itself already quite useful.
> I guess what really is throwing us here is the use of "nat". Isn't
> this really more like one of the custom remote-foo.c targets than a
> native target? It just happens to be implemented using PowerPC/Linux
> kernel facilities spelled "ptrace" and some poking around in a PowerPC
> executable in order to implement "run". The ptrace facilities don't
> seem to be used much to talk to the SPU; new files in /proc are used
> instead. It's forking and running a PowerPC executable until it makes
> a special SPU-related syscall, and then it starts talking to the SPU.
I'll have a look at the remote-foo targets. Is it just more or less just
a matter of renaming the file, or are there significant differences?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2006-11-13 12:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 18:39 Ulrich Weigand
2006-11-11 21:19 ` Mark Kettenis
2006-11-12 15:38 ` Ulrich Weigand
2006-11-12 21:42 ` Mark Kettenis
2006-11-12 22:12 ` Daniel Jacobowitz
2006-11-13 12:27 ` Ulrich Weigand [this message]
2006-11-13 12:43 ` Mark Kettenis
2006-11-13 13:48 ` Daniel Jacobowitz
2006-11-13 19:50 ` Jim Blandy
2006-11-18 0:10 ` Ulrich Weigand
2006-11-18 6:03 ` Daniel Jacobowitz
2006-11-18 11:10 ` Ulrich Weigand
2006-11-18 16:41 ` Daniel Jacobowitz
2006-11-18 17:35 ` Mark Kettenis
2006-11-21 20:22 ` Ulrich Weigand
2006-11-21 20:40 ` Daniel Jacobowitz
2006-11-21 21:32 ` Mark Kettenis
2006-11-22 14:13 ` Ulrich Weigand
2006-11-22 18:43 ` Daniel Jacobowitz
2006-11-22 19:46 ` Ulrich Weigand
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=200611131227.kADCRe28032402@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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