a50c99bcc0
There should be no paths from a coroutine_fn to aio_poll, however in practice coroutine_mixed_fn will call aio_poll in the !qemu_in_coroutine() path. By marking mixed functions, we can track accurately the call paths that execute entirely in coroutine context, and find more missing coroutine_fn markers. This results in more accurate checks that coroutine code does not end up blocking. If the marking were extended transitively to all functions that call these ones, static analysis could be done much more efficiently. However, this is a start and makes it possible to use vrc's path-based searches to find potential bugs where coroutine_fns call blocking functions. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> |
||
|---|---|---|
| .. | ||
| qmp | ||
| clone-visitor.h | ||
| compat-policy.h | ||
| dealloc-visitor.h | ||
| error.h | ||
| forward-visitor.h | ||
| opts-visitor.h | ||
| qmp-event.h | ||
| qobject-input-visitor.h | ||
| qobject-output-visitor.h | ||
| string-input-visitor.h | ||
| string-output-visitor.h | ||
| type-helpers.h | ||
| util.h | ||
| visitor-impl.h | ||
| visitor.h | ||