Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: mark.kettenis@xs4all.nl (Mark Kettenis)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc/rfa] [1/4] SPU enhancements: preparation
Date: Fri, 15 Jun 2007 15:54:00 -0000	[thread overview]
Message-ID: <200706151554.l5FFsMCe030611@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <200706151549.l5FFnwYp021247@brahms.sibelius.xs4all.nl> from "Mark Kettenis" at Jun 15, 2007 05:49:58 PM

Mark Kettenis wrote:
> > 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.
> 
> Are these files inherently non-seekable (side-effects?) or is this
> just a Linux quirk you're trying to work around?

spufs is a pseudo-filesystem implemented by the Linux kernel 
(similar to the /proc or /sys file systems); files in spufs
aren't actually real files, but provide information about
status of SPU contexts.

Most of those files simply do not support seeking; you can 
only open them, and read their contents out (once).  The
content typically represents a single data item (like the
current SPU event status).

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


      reply	other threads:[~2007-06-15 15:54 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
2007-06-12 14:40 ` Ulrich Weigand
2007-06-15 15:50 ` Mark Kettenis
2007-06-15 15:54   ` Ulrich Weigand [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=200706151554.l5FFsMCe030611@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --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