public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc64-dev@ozlabs.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/7] spufs: The SPU file system
Date: Fri, 26 Aug 2005 11:17:19 +0300	[thread overview]
Message-ID: <84144f02050826011778e1142@mail.gmail.com> (raw)
In-Reply-To: <200508260003.40865.arnd@arndb.de>

Hi Arnd,

> This is a work-in-progress version of the SPU file system.

> --- linux-cg.orig/fs/spufs/file.c     1969-12-31 19:00:00.000000000 -0500
> +++ linux-cg/fs/spufs/file.c  2005-08-25 22:27:19.503976592 -0400
> @@ -0,0 +1,716 @@
> +/*
> + * SPU file system -- file contents
> +/* low-level mailbox write */
> +size_t spu_wbox_write(struct spu *spu, u32 data)
> +{
> +     int ret;
> +
> +     spin_lock_irq(&spu->register_lock);
> +
> +     if (in_be32(&spu->problem->mb_stat_R) & 0x00ff00) {
> +             /* we have space to write wbox_data to */
> +             out_be32(&spu->problem->spu_mb_W, data);
> +             ret = 4;
> +     } else {
> +             /* make sure we get woken up by the interrupt when space
> +                becomes available */
> +             out_be64(&spu->priv1->int_mask_class2_RW,
> +                     in_be64(&spu->priv1->int_mask_class2_RW) | 0x10);

I am confused. The code is architecture specific and does device I/O. Why do
you want to put this in fs/ and not drivers/?

                                    Pekka

  reply	other threads:[~2005-08-26  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25 22:03 [PATCH 1/7] spufs: The SPU file system Arnd Bergmann
2005-08-26  8:17 ` Pekka Enberg [this message]
2005-08-28 16:44   ` Arnd Bergmann
2005-08-28 20:05     ` Pekka Enberg
2005-08-29 18:09     ` 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=84144f02050826011778e1142@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.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