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

Manage latch locking/unlocking #5

Open
qzed opened this issue Apr 6, 2021 · 0 comments
Open

Manage latch locking/unlocking #5

qzed opened this issue Apr 6, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@qzed
Copy link
Member

qzed commented Apr 6, 2021

We currently have no direct support for managing the latch lock. To do this, we need some way to manage dependencies on the dGPU (or other devices connected to the base, e.g. USB/storage) either by applications or directly by the user. One idea would be to have some sort of registry of blockers/dependencies.

Ideally we have some automatism that detects and registers apps using the dGPU (or other devices connected to the base) automatically. That's probably not easily possible, so some sort of wrapper script may be necessary, at least for registration. For applications, de-registration could maybe be done automatically by monitoring process IDs for termination (may require special handling for sub-processes).

In light of Linux being a multi-user OS, it should also be possible for users themselves to request a lock on the base, preventing detachment until no user (and no application) has such a lock.

Furthermore, some UI for inspecting/displaying those dependencies that can be shown/linked to if a detachment request was blocked would be a good idea.

@qzed qzed added the enhancement New feature or request label Apr 6, 2021
This was referenced Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant