[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v1 1/5] docs/devel: document query handle lifetimes
From: |
Alex Bennée |
Subject: |
[PATCH v1 1/5] docs/devel: document query handle lifetimes |
Date: |
Fri, 7 Feb 2020 15:01:14 +0000 |
I forgot to document the lifetime of handles in the developer
documentation. Do so now.
Signed-off-by: Alex Bennée <address@hidden>
---
docs/devel/tcg-plugins.rst | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/docs/devel/tcg-plugins.rst b/docs/devel/tcg-plugins.rst
index 718eef00f22..a05990906cc 100644
--- a/docs/devel/tcg-plugins.rst
+++ b/docs/devel/tcg-plugins.rst
@@ -51,8 +51,17 @@ about how QEMU's translation works to the plugins. While
there are
conceptions such as translation time and translation blocks the
details are opaque to plugins. The plugin is able to query select
details of instructions and system configuration only through the
-exported *qemu_plugin* functions. The types used to describe
-instructions and events are opaque to the plugins themselves.
+exported *qemu_plugin* functions.
+
+Query Handle Lifetime
+---------------------
+
+Each callback provides an opaque anonymous information handle which
+can usually be further queried to find out information about a
+translation, instruction or operation. The handles themselves are only
+valid during the lifetime of the callback so it is important that any
+information that is needed is extracted during the callback and saved
+by the plugin.
Usage
=====
--
2.20.1
- Re: [PATCH v1 2/5] plugins/core: add missing break in cb_to_tcg_flags, (continued)
- [PATCH v1 3/5] tests/plugin: prevent uninitialized warning, Alex Bennée, 2020/02/07
- [PATCH v1 4/5] target/riscv: progressively load the instruction during decode, Alex Bennée, 2020/02/07
- [PATCH v1 5/5] tests/plugins: make howvec clean-up after itself., Alex Bennée, 2020/02/07
- [PATCH v1 1/5] docs/devel: document query handle lifetimes,
Alex Bennée <=
- Re: [PATCH v1 0/5] plugins/next, no-reply, 2020/02/07
- Re: [PATCH v1 0/5] plugins/next, no-reply, 2020/02/07