<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL)" href="https://bugs.freedesktop.org/show_bug.cgi?id=90537#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL)" href="https://bugs.freedesktop.org/show_bug.cgi?id=90537">bug 90537</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 Michel Dänzer from <a href="show_bug.cgi?id=90537#c17">comment #17</a>) > My feeling is that the only proper solution might be to track the VA ranges > per GEM handle instead of per BO in the kernel. Christian, would that be > feasible in the radeon driver? I'm working on that problem for years now, tracking VA ranges per GEM handle isn't really doable either (e.g. without breaking backward compatibility). Haven't come up with a good solution so far. > BTW, I think the dmesg output would be more useful without all the debugging > output enabled. That makes it like looking for a needle in a haystack. Yeah, agree. That is a bit two much.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>