Features/TCGPlugins: Difference between revisions
No edit summary |
(more details) |
||
| Line 1: | Line 1: | ||
TCG Plugins are a new feature since 4.2 that provide the ability to run instrumentation experiments on code. They are capable for doing passive monitoring of every instruction and memory access made by the system. | TCG Plugins are a new feature since 4.2 that provide the ability to run instrumentation experiments on code. They are capable for doing passive monitoring of every instruction and memory access made by the system. | ||
Full details can be found in | Full details can be found in {{src|path=docs/devel/plugins.rst}} | ||
= Building = | = Building = | ||
| Line 8: | Line 8: | ||
= Running = | = Running = | ||
Multiple plugins can be loaded and each one can have arguments passed to it. | |||
$QEMU $QEMU_ARGS -plugin=libplugin.so,arg="foo",arg="bar" -d plugin -D output.plugin | |||
Revision as of 13:46, 31 October 2019
TCG Plugins are a new feature since 4.2 that provide the ability to run instrumentation experiments on code. They are capable for doing passive monitoring of every instruction and memory access made by the system.
Full details can be found in docs/devel/plugins.rst
Building
The build needs to be configured with `--enable-plugins`
Running
Multiple plugins can be loaded and each one can have arguments passed to it.
$QEMU $QEMU_ARGS -plugin=libplugin.so,arg="foo",arg="bar" -d plugin -D output.plugin