On Mon, Sep 15, 2014 at 05:12:12PM +0200, Pavel Hrdina wrote: > This patch series introduce new cputune event to inform > management applications about every change of cputune values > for running domains. > > There is missing documentation for all events so the documentation > for this event will be part of the patches to document all events. Do you have any background on the motivation for this feature ? It would help to understand the use case better in order to decide whether this is the right approach for the events. Specifically I am wondering whether returning all the values in the event is the best way. The alternative would be to have a generic "resource tunable changed" event where we just specify the type of data that changed, and allow the app to then fetch the new values if they actually want them. This would let us deal with all the resource tunables in a single event, isntead of having to add more events for memory tunables, numa tunables, disk I/O, net I/O etc. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list