monitor: Use getter/setter functions for cur_mon
cur_mon really needs to be coroutine-local as soon as we move monitor command handlers to coroutines and let them yield. As a first step, just remove all direct accesses to cur_mon so that we can implement this in the getter function later. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-Id: <20201005155855.256490-4-kwolf@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com>
This commit is contained in:
committed by
Markus Armbruster
parent
87e6f4a4d6
commit
947e47448d
@@ -20,6 +20,7 @@
|
||||
*/
|
||||
int qemu_vprintf(const char *fmt, va_list ap)
|
||||
{
|
||||
Monitor *cur_mon = monitor_cur();
|
||||
if (cur_mon) {
|
||||
return monitor_vprintf(cur_mon, fmt, ap);
|
||||
}
|
||||
@@ -48,7 +49,7 @@ int qemu_printf(const char *fmt, ...)
|
||||
int qemu_vfprintf(FILE *stream, const char *fmt, va_list ap)
|
||||
{
|
||||
if (!stream) {
|
||||
return monitor_vprintf(cur_mon, fmt, ap);
|
||||
return monitor_vprintf(monitor_cur(), fmt, ap);
|
||||
}
|
||||
return vfprintf(stream, fmt, ap);
|
||||
}
|
||||
|
Reference in New Issue
Block a user