提交 ae37001d 编写于 作者: G Guido Günther

Document that ff callbacks need to be invoked from a clean stack.

Also fix a typo.
上级 cdd5ef7b
...@@ -2243,13 +2243,15 @@ typedef void (*virEventHandleCallback)(int watch, int fd, int events, void *opaq ...@@ -2243,13 +2243,15 @@ typedef void (*virEventHandleCallback)(int watch, int fd, int events, void *opaq
* @opaque: user data to pass to the callback * @opaque: user data to pass to the callback
* @ff: the callback invoked to free opaque data blob * @ff: the callback invoked to free opaque data blob
* *
* Part of the EventImpl, this callback Adds a file handle callback to * Part of the EventImpl, this callback adds a file handle callback to
* listen for specific events. The same file handle can be registered * listen for specific events. The same file handle can be registered
* multiple times provided the requested event sets are non-overlapping * multiple times provided the requested event sets are non-overlapping
* *
* If the opaque user data requires free'ing when the handle * If the opaque user data requires free'ing when the handle
* is unregistered, then a 2nd callback can be supplied for * is unregistered, then a 2nd callback can be supplied for
* this purpose. * this purpose. This callback needs to be invoked from a clean stack.
* If 'ff' callbacks are invoked directly from the virEventRemoveHandleFunc
* they will likely deadlock in libvirt.
* *
* Returns a handle watch number to be used for updating * Returns a handle watch number to be used for updating
* and unregistering for events * and unregistering for events
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册