| commit | ac7798f280b716701489594fe5bc7864b26a99e6 | |
| author | Emanuele Giuseppe Esposito <eesposit@redhat.com> | |
| Thu, 3 Mar 2022 15:15:47 +0000 (3 10:15 -0500) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Fri, 4 Mar 2022 17:18:25 +0000 (4 18:18 +0100) | ||
| tree | 619a109c2c0a6f6ebc2e4fd5647f418e6ba1d226 | treesnapshot (tar.gz zip) |
| parent | 6538692e2802666926e62d9309ddddda5ec9dc3b | commitdiff |
main loop: macros to mark GS and I/O functions
Righ now, IO_CODE and IO_OR_GS_CODE are nop, as there isn't
really a way to check that a function is only called in I/O.
On the other side, we can use qemu_in_main_thread() to check if
we are in the main loop.
The usage of macros makes easy to extend them in the future without
making changes in all callers. They will also visually help understanding
in which category each function is, without looking at the header.
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Message-Id: <20220303151616.325444-3-eesposit@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Righ now, IO_CODE and IO_OR_GS_CODE are nop, as there isn't
really a way to check that a function is only called in I/O.
On the other side, we can use qemu_in_main_thread() to check if
we are in the main loop.
The usage of macros makes easy to extend them in the future without
making changes in all callers. They will also visually help understanding
in which category each function is, without looking at the header.
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Message-Id: <20220303151616.325444-3-eesposit@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| include/qemu/main-loop.h | diffblobblamehistory |