In patch 5 (and others), could we extend wined3d_texture_vk_barrier to handle barriers before the blits, and not worry about barriers after?
I guess yes, but it brings its own problems. This question is why I'd split of the blit/clear into a separate series.
I am concerned about the cost (and code required) of iterating over every subresource in wined3d_texture_vk_barrier - which is something that would be necessary if we want to make it support blits in general. The common case of the entire image being in one layout could certainly be optimized though.
We can't always transition the entire resource. A blit may happen between two subresources of the same texture.