-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a GPU acceleration toggle #8553
Comments
Creating this before GPU acceleration exists is a bad idea (why have an option that misleads the user?). |
Make an issue once this becomes a real toggle to make. |
This issue was intended to describe something that needs to be done eventually. It should have been labeled as “blocked” to clarify that. Some other bug tracking systems, such as Bugzilla, have a concept of one issue being blocked on another, which would make this obvious. |
Can just use
Can just use the |
How to file a helpful issue
The problem you're addressing (if any)
Users need to be able to control which qubes have access to GPU acceleration. While GPU acceleration in Qubes OS is intended to be reasonably secure once implemented, it still introduces extra attack surface and so will be disabled by default.
This can be implemented even before GPU acceleration is — enabling GPU acceleration will be a no-op in this case.
The solution you'd like
A toggle in the GUI to control GPU acceleration.
The value to a user, and who that user might be
Users who wish to use GPU acceleration will be able to do so, once GPU acceleration has been implemented.
Blocked on #8552
The text was updated successfully, but these errors were encountered: