On Wed, Apr 3, 2019 at 8:38 AM Marek Olšák <mar...@gmail.com> wrote: > > On Tue, Apr 2, 2019 at 2:14 PM Eric Anholt <e...@anholt.net> wrote: >> >> Ilia Mirkin <imir...@alum.mit.edu> writes: >> >> > Shouldn't this sort of decision be left up to the driver? If the >> > driver would like to use CS for blits, fine, but why not let it blit >> > in the most optimal way possible and force it to use a compute shader? >> >> Yeah, commit messages require an explanation of why a change is being >> made. > > > We plan to create vaapi contexts with PIPE_CONTEXT_COMPUTE_ONLY for better > GPU multitasking. > > RadeonSI uses async compute queues if PIPE_CONTEXT_COMPUTE_ONLY is set, so it > can't do any graphics stuff, not even blit. (pipe_context::blit is NULL)
Makes sense. Sounds like one of those would be a better condition than the mere existence of compute support then? -ilia _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
