<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT BYT] "HW access outside of RPM atomic section" on driver unload" href="https://bugs.freedesktop.org/show_bug.cgi?id=95634#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT BYT] "HW access outside of RPM atomic section" on driver unload" href="https://bugs.freedesktop.org/show_bug.cgi?id=95634">bug 95634</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>So this would catch the straightforward load/unload, it would not if any work was done in between that left the default context uninitialised. We can either flag it as initialised and never load the golden render state for the default context (which is valid as it should never be executed itself, and the render state should be applied to all other contexts on first use), or we go full monty and follow my planned route of making suspend lockless and not emitting a batch here at all for !execlists: <a href="https://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=tasklet&id=f8fff5e32923a56ea5ce73a4ae68968bc60b70c8">https://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=tasklet&id=f8fff5e32923a56ea5ce73a4ae68968bc60b70c8</a> First two steps are pretty simple though...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>