<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [RV620][RV630][RS880] GPU hangs using UVD hardware acceleration" href="https://bugs.freedesktop.org/show_bug.cgi?id=85320#c46">Comment # 46</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [RV620][RV630][RS880] GPU hangs using UVD hardware acceleration" href="https://bugs.freedesktop.org/show_bug.cgi?id=85320">bug 85320</a> from <a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> Christian König</a> <pre>(In reply to Nicola Mori from <a href="show_bug.cgi?id=85320#c44">comment #44</a>) > The new patch works also for me. A couple of questions, Christian: does the > patch remove some features? Do you think to mainline it or rather implement > a different fix now that the problem seems to be better defined? Thanks. Instead of submitting the commands to the hardware directly with semaphores to sync between the GFX and UVD engines we block until the dependent task is completed. That's rather bad in a couple of different cases, for example doing 3D gaming and video playback at the same time. What essentially happens is instead of keeping UVD and GFX busy all the same time (and only occasionally block one engine waiting the other one) you do it more like this: 1. Run UVD job. 2. Wait for UVD to finish. 3. Run GFX. 4. Wait for GFX to finish. 5. Run UVD 6. Wait for UVD to finish. ....</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>