From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc/rfa] [1/4] SPU enhancements: preparation
Date: Mon, 04 Jun 2007 19:27:00 -0000 [thread overview]
Message-ID: <20070604192648.GA23516@caradoc.them.org> (raw)
In-Reply-To: <200706021931.l52JVBZQ005084@d12av02.megacenter.de.ibm.com>
On Sat, Jun 02, 2007 at 09:31:11PM +0200, Ulrich Weigand wrote:
> Hello,
>
> this is a small fix in preparation for adding extended SPU query support.
> Some files in spufs accessed via the spu_proc_xfer_spu routines in
> spu-linux-nat.c and gdbserver/spu-low.c are non-seekable. Currently,
> any attempt to access those at non-zero offset results in a failure.
>
> However, that is a problem when trying to use those files via the
> target object mechanism. For example, the target_read routine will
> first read a chunk at offset zero (which succeeds, and in fact is
> generally sufficient to retrieve the full contents as the non-seekable
> files are small). But then it attempts a second read at an offset
> corresponding to the length of the first chunk read, which now fails.
>
> This patch changes spu_proc_xfer_spu to simply return zero (i.e. no
> more data available) on any attempt to access a non-seekable spufs
> file at non-zero offset.
>
> Tested on spu-elf in conjunction with the other patches.
Seems reasonable to me.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-04 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 19:31 Ulrich Weigand
2007-06-04 19:27 ` Daniel Jacobowitz [this message]
2007-06-12 14:40 ` Ulrich Weigand
2007-06-15 15:50 ` Mark Kettenis
2007-06-15 15:54 ` 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=20070604192648.GA23516@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.com \
/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