From: Arnd Bergmann <arnd@arndb.de>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
cpufreq@lists.linux.org.uk, linuxppc-dev@ozlabs.org,
Jeremy Kerr <jk@ozlabs.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
cbe-oss-dev@ozlabs.org
Subject: Re: powerpc/cell/cpufreq: add spu aware cpufreq governor
Date: Tue, 8 Jul 2008 08:43:43 +0200 [thread overview]
Message-ID: <200807080843.43674.arnd@arndb.de> (raw)
In-Reply-To: <20080707213105.GD4997@codemonkey.org.uk>
On Monday 07 July 2008, Dave Jones wrote:
> One question I do have though, is how userspace scripts are supposed
> to know they're to echo cbe_spu_governor into the relevant parts of
> sysfs. I've not used anything with a cell. Do they expose the SPUs
> as regular CPUs, or do they show up in a different part of the tree?
An SPU is very different from a CPU from the user perspective.
SPUs show up in /sys/devices/system/spus, and if a user wants to access
them, the "spufs" file system needs to be mounted in the system, by
convention on /spu.
Arnd <><
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
cpufreq@lists.linux.org.uk, linuxppc-dev@ozlabs.org,
Jeremy Kerr <jk@ozlabs.org>,
cbe-oss-dev@ozlabs.org
Subject: Re: powerpc/cell/cpufreq: add spu aware cpufreq governor
Date: Tue, 8 Jul 2008 08:43:43 +0200 [thread overview]
Message-ID: <200807080843.43674.arnd@arndb.de> (raw)
In-Reply-To: <20080707213105.GD4997@codemonkey.org.uk>
On Monday 07 July 2008, Dave Jones wrote:
> One question I do have though, is how userspace scripts are supposed
> to know they're to echo cbe_spu_governor into the relevant parts of
> sysfs. =A0I've not used anything with a cell. Do they expose the SPUs
> as regular CPUs, or do they show up in a different part of the tree?
An SPU is very different from a CPU from the user perspective.
SPUs show up in /sys/devices/system/spus, and if a user wants to access
them, the "spufs" file system needs to be mounted in the system, by
convention on /spu.=20
Arnd <><
next prev parent reply other threads:[~2008-07-08 6:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 15:02 powerpc/cell/cpufreq: add spu aware cpufreq governor Arnd Bergmann
2008-07-07 15:02 ` Arnd Bergmann
2008-07-07 17:17 ` [Cbe-oss-dev] " Eric Blossom
2008-07-07 21:02 ` Arnd Bergmann
2008-07-07 21:02 ` Arnd Bergmann
2008-07-07 21:31 ` Dave Jones
2008-07-07 21:31 ` Dave Jones
2008-07-08 6:43 ` Arnd Bergmann [this message]
2008-07-08 6:43 ` Arnd Bergmann
2008-07-08 15:27 ` Dave Jones
2008-07-08 15:27 ` Dave Jones
2008-07-09 3:41 ` Benjamin Herrenschmidt
2008-07-09 3:57 ` Dave Jones
2008-07-10 18:05 ` Dominik Brodowski
2008-07-10 18:05 ` Dominik Brodowski
2008-07-10 21:05 ` Arnd Bergmann
2008-07-10 21:16 ` Dominik Brodowski
2008-07-09 5:18 ` Benjamin Herrenschmidt
2008-07-09 6:29 ` Dave Jones
2008-07-15 13:02 ` Arnd Bergmann
2008-07-15 13:02 ` Arnd Bergmann
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=200807080843.43674.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.