Lines Matching full:plugin

22 your plugin upstream so they can be updated if/when the API changes.
24 All plugins need to declare a symbol which exports the plugin API
29 The core code will refuse to load a plugin that doesn't export a
30 ``qemu_plugin_version`` symbol or if plugin version is outside of QEMU's
34 ``qemu_plugin_install`` method of a plugin will detail the minimum and
47 by the plugin.
49 Plugin life cycle
52 First the plugin is loaded and the public qemu_plugin_install function
53 is called. The plugin will then register callbacks for various plugin
58 When a registered event occurs the plugin callback is invoked. The
60 translation event the plugin has an option to enumerate the
79 The plugin architecture actively avoids leaking implementation details
82 details are opaque to plugins. The plugin is able to query select
114 instrument the next instruction as well. See the ``execlog.c`` plugin
142 this we acquire a lock when called from plugin code. We also keep the
158 We support the uninstallation of a plugin at any time (e.g. from
159 plugin callbacks). This allows plugins to remove themselves if they no
162 requested. The plugin isn't completely uninstalled until the safe work
165 Plugin API
169 ``include/qemu/qemu-plugin.h``. Please ensure any updates to the API
172 .. kernel-doc:: include/qemu/qemu-plugin.h