Re: [PATCH V9 03/17] iothread: tracking iothread users with holder name

[Stefan Hajnoczi <stefanha@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

On Wed, Jun 24, 2026 at 03:08:37PM +0800, Zhang Chen wrote:
> @@ -70,6 +71,9 @@ DECLARE_INSTANCE_CHECKER(IOThread, IOTHREAD,
>  char *iothread_get_id(IOThread *iothread);
>  IOThread *iothread_by_id(const char *id);
>  AioContext *iothread_get_aio_context(IOThread *iothread);
> +AioContext *iothread_ref_and_get_aio_context(IOThread *iothread,
> +                                             const IOThreadHolder *holder);
> +void iothread_put_aio_context(IOThread *iothread, const IOThreadHolder *holder);

There should be doc comments for these new APIs. One constraint that
should be documented is that these APIs are not thread-safe and must be
called under the Big QEMU Lock (BQL) (this is necessary both to avoid
holders list race conditions and because object_unref() can invoke
finalize callbacks that expect to run under the BQL).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]