User talk:Masterzorag: Difference between revisions
Jump to navigation
Jump to search
Masterzorag (talk | contribs) (SPU Problems on Linux 3.x, OpenCL related) |
Masterzorag (talk | contribs) m (Tested Linux 3.5.3) |
||
| Line 12: | Line 12: | ||
* 3.3.3 falls into 'possible circular locking dependency detected' and slowdown runtime | * 3.3.3 falls into 'possible circular locking dependency detected' and slowdown runtime | ||
* 3.4.6 falls into 'possible circular locking dependency detected' and slowdown runtime | * 3.4.6 falls into 'possible circular locking dependency detected' and slowdown runtime | ||
* 3.5. | * 3.5.3 falls into 'possible circular locking dependency detected' and slowdown runtime | ||
When program runs, OpenCL builtin function to query available SPEs reply 8 (!), so seems that the issue is OpenCL related. | |||
Revision as of 16:24, 28 August 2012
SPU Problems on Linux 3.x, OpenCL related
As far as I know, I'm the only coding OpenCL on the Cell here, if someone want to test something be warned that it's stable until 3.2 branch. This due some spufs changes that ppc-kernel-devs are (maybe) trying to fix, so now latest 3.3/3.4 branches falls into 'possible circular locking dependency detected' and slowdown runtime. Even disabling lock debugging it slowdowns runtime without debug messages, it happens even with OpenCL samples from IBM.
http://permalink.gmane.org/gmane.linux.ports.ppc.embedded/50547
Tested kernels:
- 3.2.23 works fine
- 3.3.3 falls into 'possible circular locking dependency detected' and slowdown runtime
- 3.4.6 falls into 'possible circular locking dependency detected' and slowdown runtime
- 3.5.3 falls into 'possible circular locking dependency detected' and slowdown runtime
When program runs, OpenCL builtin function to query available SPEs reply 8 (!), so seems that the issue is OpenCL related.