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
Add notification events for add/remove device definitions #27
Comments
I'm wondering whether we can combine this with the 'callout' interface suggested in #20 -- we need a mechanism to invoke scripts etc. for that as well. A post-create/post-remove callout should basically cover the add/remove events. If we do not introduce a more formal message via DBus, would the ability to invoke a custom script be already enough to process state changes? |
That's not a bad idea. It would probably work for what I need, depending on exactly how it is implemented.
|
Looking through old issues... I'm wondering whether the callout feature as it is merged does what you need? |
A notification script should hopefully suffice? :) |
I'm mostly asking whether we can close this issue :) |
yep, I think we can close it. |
A management app like libvirt would like to be able to monitor new or removed mediated device definitions. Currently, we have resort to something like periodically polling
mdevctl list --defined
to detect new or removed devices. It would be nice if we could instead listen for events indicating that a device is defined or undefined.I envision something similar in concept to udev 'add' or 'remove' events for regular devices. Perhaps DBus could be the mechanism for announcing these events? I'm open to other ideas.
The text was updated successfully, but these errors were encountered: