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 22:16:21 +1000 [thread overview]
Message-ID: <20130423121620.GB27200@concordia> (raw)
In-Reply-To: <20130423140116.0a40c2c6@samson>
On Tue, Apr 23, 2013 at 02:01:16PM +0200, Dennis Schridde wrote:
> Am Mon, 22 Apr 2013 18:44:13 +0200
> schrieb Dennis Schridde <devurandom@gmx.net>:
> > [4.] Kernel information
> >
> > [4.1.] Kernel version (from /proc/version):
> > I am using the Linux 3.8.8 kernel (vanilla-sources-3.8.8 on
> > Gentoo/Linux): # cat /proc/version
> > Linux version 3.8.8 (root@blade00) (gcc version 4.7.2 (Gentoo
> > 4.7.2-r1 p1.5, pie-0.5.5) ) #2 SMP Mon Apr 22 18:21:20 CEST 2013
>
> Actually this is only partially correct.
>
> I applied following patch by Grant Likely
> <grant.likely@secretlab.ca> to fix some IRQ mapping problems:
Ah yes, I forgot I also have basically the same patch. I've just sent it
to the list.
We appear to have a number of problems with the irq mapping on cell,
that patch fixes the worst of them but there are more.
cheers
next prev parent reply other threads:[~2013-04-23 12:16 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 [this message]
2013-04-23 12:41 ` Dennis Schridde
2013-04-23 12:53 ` Michael Ellerman
2013-04-23 13:24 ` Michael Ellerman
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=20130423121620.GB27200@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