From: Jeremy Kerr <jk@ozlabs.org>
To: Sombat Tragolgosol <sombat3960@gmail.com>, Linuxppc-dev@lists.ozlabs.org
Cc: geoff@infradead.org
Subject: Re: SPU not working for kernel 4.9, 4.10, 4.11a and 4.12
Date: Tue, 23 May 2017 18:01:34 +1000 [thread overview]
Message-ID: <32cc4462-0a47-ee5a-7429-af5428126743@ozlabs.org> (raw)
In-Reply-To: <c16c0ba8-aa6d-0dbd-28d2-d73fda643ae5@ozlabs.org>
Hi all,
> Looks like this also happens with the simple spu_run test:
>
> https://github.com/jk-ozlabs/spufs-testsuite/blob/master/tests/03-spu_run/01-spu_run.c
>
> ... might need some debugging here, I'll update if I find anything.
And it appears we're stuck in the POLL_WHILE_FALSE() loop in
wait_tag_complete() called from restore_lscsa().
Because spufs itself has been fairly static, I suspect some other change
has meant that MFC DMAs aren't working; so at this point, a bisect might
be the best way forward. Do you see the exact same behaviour on 4.9 (but
4.8 works?)
Cheers,
Jeremy
next prev parent reply other threads:[~2017-05-23 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 9:30 SPU not working for kernel 4.9, 4.10, 4.11a and 4.12 Sombat Tragolgosol
2017-05-23 5:21 ` Jeremy Kerr
2017-05-23 8:01 ` Jeremy Kerr [this message]
2017-05-24 0:58 ` Michael Ellerman
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=32cc4462-0a47-ee5a-7429-af5428126743@ozlabs.org \
--to=jk@ozlabs.org \
--cc=Linuxppc-dev@lists.ozlabs.org \
--cc=geoff@infradead.org \
--cc=sombat3960@gmail.com \
/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