rendervulkan: Use general queue for Intel devices

During forced composition, work sent to the compute-only queue is
starved for resources, competing with the general queue. When resources
are freed up for the compute-only queue, the general queue is waiting at
a sync point for the compute work to finish.

This can be beneficial for some workloads, but it causes applications
running with gamescope's forced composition to slow down when the
queues are competing for resources.

By forcing the compositing work to be done in the general queue, we
avoid the wait for sync points and the performance loss is not observed.

Signed-off-by: Casey Bowman <[email protected]>

Author: cgbowman

src/rendervulkan.cpp

@@ -379,7 +379,8 @@ bool CVulkanDevice::selectPhysDev(VkSurfaceKHR surface)
 				m_generalQueueFamily = generalIndex;
 				m_physDev = cphysDev;
 
-				if ( env_to_bool( getenv( "GAMESCOPE_FORCE_GENERAL_QUEUE" ) ) )
+				if ( env_to_bool( getenv( "GAMESCOPE_FORCE_GENERAL_QUEUE" ) ) ||
+				     deviceProperties.vendorID == 32902) /* Intel */
 					m_queueFamily = generalIndex;
 			}
 		}