r300: move HyperZ blacklist to driconf
r300: move HyperZ blacklist to driconf
Only one process can use HyperZ at a time, so when HyperZ was enabled for R5xx, a blacklist got introduced to prevent X and window managers to steal HyperZ access so that we can save it for apps where we care more for performance (like games or benchmarks
I don't really have time to check the other apps listed there, so I'm kind of hoping some interested users might figure out how to benchmark gnome-shell/KWin/compiz/etc... to check if it would make sense to actually let it have HyperZ access (if we can get at least 5+ percent speedup for standard desktop usage, it might be actually worth it considering the GPUs nowadays feel slow even for normal desktop work). But anyway even if the list ultimately stays the same I plan to introduce some more app-specific overrides (for example to fix #332) so I'll be making more use of driconf and this seems like a step in the right direction.
Framework mostly copied from radeonsi...