Skip to content
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

Open
DemiMarie opened this issue Sep 27, 2023 · 4 comments
Open

Provide a GPU acceleration toggle #8553

DemiMarie opened this issue Sep 27, 2023 · 4 comments
Labels
C: GPU acceleration C: manager/widget P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. S: blocked Status: blocked. Work on this issue is currently blocked.

Comments

@DemiMarie
Copy link

DemiMarie commented Sep 27, 2023

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

@DemiMarie DemiMarie added T: enhancement C: manager/widget P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. labels Sep 27, 2023
@DemiMarie DemiMarie added this to the Release 4.3 milestone Sep 27, 2023
@DemiMarie DemiMarie moved this to Todo in GPU acceleration Sep 27, 2023
@andrewdavidwong andrewdavidwong removed this from the Release 4.3 milestone Sep 27, 2023
@marmarta
Copy link
Member

Creating this before GPU acceleration exists is a bad idea (why have an option that misleads the user?).

@marmarta
Copy link
Member

Make an issue once this becomes a real toggle to make.

@marmarta marmarta closed this as not planned Won't fix, can't repro, duplicate, stale Oct 15, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in GPU acceleration Oct 15, 2023
@DemiMarie
Copy link
Author

Creating this before GPU acceleration exists is a bad idea (why have an option that misleads the user?).

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.

@andrewdavidwong andrewdavidwong added the S: blocked Status: blocked. Work on this issue is currently blocked. label Oct 15, 2023
@andrewdavidwong
Copy link
Member

It should have been labeled as “blocked” to clarify that.

Can just use S: blocked for 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 the S: blocked label and say in the issue what it's blocked by. If the other (blocking) issue doesn't exist yet, which seems to be the case here, then that feature wouldn't help you anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: GPU acceleration C: manager/widget P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. S: blocked Status: blocked. Work on this issue is currently blocked.
Projects
None yet
Development

No branches or pull requests

3 participants