Fix KMS initialization in virtualization environments with separate render/display nodes #2048
+14
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This ensures the function's semantics align with its name and simplifies the implementation of subsequent patch.
In certain SR-IOV virtualization setups, rendering and display functions are split across different DRM nodes. A typical case is using an Intel iGPU Virtual Function (VF) as the Vulkan render device, while using virtio-GPU as the KMS device for output. If the detected Vulkan primary device is found to be unsatisfactory for KMS, the backend will now attempt to initialize an alternative KMS-capable device to ensure a working display.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves device selection logic to support environments where the rendering device and display device are separate, which is common in SR-IOV and Virtualization setups (e.g., Intel iGPU VF for rendering + virtio-GPU for display).