<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [hawaii, radeonsi, clover] Running Piglit cl/program/execute/{,tail-}calls{,-struct,-workitem-id}.cl cause GPU VM error and ring stalled GPU lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=105113#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [hawaii, radeonsi, clover] Running Piglit cl/program/execute/{,tail-}calls{,-struct,-workitem-id}.cl cause GPU VM error and ring stalled GPU lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=105113">bug 105113</a> from <a class="email" href="mailto:mail@maciej.szmigiero.name" title="Maciej S. Szmigiero <mail@maciej.szmigiero.name>"> Maciej S. Szmigiero</a> <pre>There are really two issues at play here: 1) If the LLVM-generated code cannot be run properly then it should be simply rejected by whatever is actually in charge of submitting it to the GPU (I guess this would be Mesa?). This way an application will know it cannot use OpenCL for computation, at least not with this compute kernel. Instead, it currently looks like many of these test run but give incorrect results, which is obviously rather bad. 2) Some (previous) Mesa + LLVM versions generate a command stream that crashes the GPU and, as far as I can remember, sometimes even lockup the whole machine. It should not be possible to crash the GPU, regardless how incorrect a command stream that userspace sends to it is - because otherwise it is possible for an unprivileged user with GPU access to DoS the machine.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>