Re: [PATCH v2 1/5] system/cpus: rename qemu_mutex_lock_iothread() to bql_lock()

[Bernhard Beschow <shentey@xxxxxxxxx>]

Am 12. Dezember 2023 15:39:00 UTC schrieb Stefan Hajnoczi <stefanha@xxxxxxxxxx>:
>The Big QEMU Lock (BQL) has many names and they are confusing. The
>actual QemuMutex variable is called qemu_global_mutex but it's commonly
>referred to as the BQL in discussions and some code comments. The
>locking APIs, however, are called qemu_mutex_lock_iothread() and
>qemu_mutex_unlock_iothread().
>
>The "iothread" name is historic and comes from when the main thread was
>split into into KVM vcpu threads and the "iothread" (now called the main

Duplicate "into" here.

>loop thread). I have contributed to the confusion myself by introducing
>a separate --object iothread, a separate concept unrelated to the BQL.
>
>The "iothread" name is no longer appropriate for the BQL. Rename the
>locking APIs to:
>- void bql_lock(void)
>- void bql_unlock(void)
>- bool bql_locked(void)
>
>There are more APIs with "iothread" in their names. Subsequent patches
>will rename them. There are also comments and documentation that will be
>updated in later patches.
>
>Signed-off-by: Stefan Hajnoczi <stefanha@xxxxxxxxxx>
>Reviewed-by: Paul Durrant <paul@xxxxxxx>
>Acked-by: Fabiano Rosas <farosas@xxxxxxx>
>Acked-by: David Woodhouse <dwmw@xxxxxxxxxxxx>
>Reviewed-by: Cédric Le Goater <clg@xxxxxxxx>
>Acked-by: Peter Xu <peterx@xxxxxxxxxx>
>Acked-by: Eric Farman <farman@xxxxxxxxxxxxx>
>Reviewed-by: Harsh Prateek Bora <harshpb@xxxxxxxxxxxxx>