From: Michael Ellerman <michael@ellerman.id.au>
To: Dennis Schridde <devurandom@gmx.net>
Cc: cbe-oss-dev@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org,
arnd@arndb.de
Subject: Re: PROBLEM: Only 2 of 4 cores used on IBM Cell blades and no threads shown in spufs
Date: Tue, 23 Apr 2013 23:24:36 +1000 [thread overview]
Message-ID: <20130423132436.GB1078@concordia> (raw)
In-Reply-To: <1470334.YUWOQ37ijW@ernie>
On Mon, Apr 22, 2013 at 06:44:13PM +0200, Dennis Schridde wrote:
> Hello!
>
>
> [1.] One line summary of the problem:
> .. no threads shown in spufs
So I think I've got this one fixed, this works for me, can you test it
please?
I'll send a proper patch in the morning.
cheers
diff --git a/arch/powerpc/platforms/cell/spufs/inode.c b/arch/powerpc/platforms/cell/spufs/inode.c
index 3f3bb4c..35f77a4 100644
--- a/arch/powerpc/platforms/cell/spufs/inode.c
+++ b/arch/powerpc/platforms/cell/spufs/inode.c
@@ -99,6 +99,7 @@ spufs_new_inode(struct super_block *sb, umode_t mode)
if (!inode)
goto out;
+ inode->i_ino = get_next_ino();
inode->i_mode = mode;
inode->i_uid = current_fsuid();
inode->i_gid = current_fsgid();
next prev parent reply other threads:[~2013-04-23 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 16:44 PROBLEM: Only 2 of 4 cores used on IBM Cell blades and no threads shown in spufs Dennis Schridde
2013-04-23 9:12 ` Michael Ellerman
2013-04-23 11:51 ` Dennis Schridde
2013-04-23 13:16 ` Dennis Schridde
2013-04-23 13:19 ` Michael Ellerman
2013-05-17 15:46 ` Dennis Schridde
2013-05-22 3:37 ` Michael Ellerman
2013-04-23 12:01 ` Dennis Schridde
2013-04-23 12:16 ` Michael Ellerman
2013-04-23 12:41 ` Dennis Schridde
2013-04-23 12:53 ` Michael Ellerman
2013-04-23 13:24 ` Michael Ellerman [this message]
2013-04-23 18:13 ` Dennis Schridde
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=20130423132436.GB1078@concordia \
--to=michael@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@lists.ozlabs.org \
--cc=devurandom@gmx.net \
--cc=linuxppc-dev@lists.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