qmp: Optionally run handlers in coroutines
v5 cover qmp: Optionally run handlers in coroutines
Some QMP command handlers can block the main loop for a relatively long time, for example because they perform some I/O. This is quite nasty. Allowing such handlers to run in a coroutine where they can yield (and therefore release the BQL) while waiting for an event such as I/O completion solves the problem.
This series adds the infrastructure to allow this and switches block_resize to run in a coroutine as a first example.
This is an alternative solution to Marc-André's "monitor: add asynchronous command type" series.
v5:
- Improved comments and documentation [Markus]
v4:
- Forbid 'oob': true, 'coroutine': true [Markus]
- Removed Python type hints [Markus]
- Introduced separate bool qmp_dispatcher_co_shutdown to make it clearer how a shutdown request is signalled to the dispatcher [Markus]
- Allow using aio_poll() with iohandler_ctx and use that instead of aio_bh_poll() [Markus]
- Removed coroutine_fn from qmp_block_resize() again because at least one caller (HMP) calls it outside of coroutine context [Markus]
- Tried to make the synchronisation between dispatcher and the monitor thread clearer, and fixed a race condition
- Improved documentation and comments
v3:
- Fix race between monitor thread and dispatcher that could schedule the dispatcher coroutine twice if a second requests comes in before the dispatcher can wake up [Patchew]
v2:
- Fix typo in a commit message [Eric]
- Use hyphen instead of underscore for the test command [Eric]
- Mark qmp_block_resize() as coroutine_fn [Stefan]
Kevin Wolf (4):
qapi: Add a 'coroutine' flag for commands
vl: Initialise main loop earlier
qmp: Move dispatcher to a coroutine
block: Mark 'block_resize' as coroutine
qapi/block-core.json | 3 +- docs/devel/qapi-code-gen.txt | 11 +++ include/qapi/qmp/dispatch.h | 2 + monitor/monitor-internal.h | 6 +- monitor/monitor.c | 55 +++++++++-- monitor/qmp.c | 122 ++++++++++++++++++------ qapi/qmp-dispatch.c | 44 ++++++++- qapi/qmp-registry.c | 3 + tests/test-qmp-cmds.c | 4 + util/aio-posix.c | 7 +- vl.c | 10 +- scripts/qapi/commands.py | 10 +- scripts/qapi/doc.py | 2 +- scripts/qapi/expr.py | 10 +- scripts/qapi/introspect.py | 2 +- scripts/qapi/schema.py | 9 +- tests/qapi-schema/test-qapi.py | 7 +- tests/Makefile.include | 1 + tests/qapi-schema/oob-coroutine.err | 2 + tests/qapi-schema/oob-coroutine.json | 2 + tests/qapi-schema/oob-coroutine.out | 0 tests/qapi-schema/qapi-schema-test.json | 1 + tests/qapi-schema/qapi-schema-test.out | 2 + 23 files changed, 254 insertions(+), 61 deletions(-) create mode 100644 tests/qapi-schema/oob-coroutine.err create mode 100644 tests/qapi-schema/oob-coroutine.json create mode 100644 tests/qapi-schema/oob-coroutine.out
Signature · 1 line
2.20.1
PATCH v5 1/4 qapi: Add a 'coroutine' flag for commands
This patch adds a new 'coroutine' flag to QMP command definitions that tells the QMP dispatcher that the command handler is safe to be run in a coroutine.
The documentation of the new flag pretends that this flag is already used as intended, which it isn't yet after this patch. We'll implement this in another patch in this series.
--- docs/devel/qapi-code-gen.txt | 11 +++++++++++ include/qapi/qmp/dispatch.h | 1 + tests/test-qmp-cmds.c | 4 ++++ scripts/qapi/commands.py | 10 +++++++--- scripts/qapi/doc.py | 2 +- scripts/qapi/expr.py | 10 ++++++++-- scripts/qapi/introspect.py | 2 +- scripts/qapi/schema.py | 9 ++++++--- tests/qapi-schema/test-qapi.py | 7 ++++--- tests/Makefile.include | 1 + tests/qapi-schema/oob-coroutine.err | 2 ++ tests/qapi-schema/oob-coroutine.json | 2 ++ tests/qapi-schema/oob-coroutine.out | 0 tests/qapi-schema/qapi-schema-test.json | 1 + tests/qapi-schema/qapi-schema-test.out | 2 ++ 15 files changed, 51 insertions(+), 13 deletions(-) create mode 100644 tests/qapi-schema/oob-coroutine.err create mode 100644 tests/qapi-schema/oob-coroutine.json create mode 100644 tests/qapi-schema/oob-coroutine.out
docs/devel/qapi-code-gen.txt +11 -0
@@ -457,6 +457,7 @@ Syntax: '*gen': false, '*allow-oob': true, '*allow-preconfig': true, + '*coroutine': true, '*if': COND, '*features': FEATURES }
@@ -581,6 +582,16 @@ before the machine is built. It defaults to false. For example: QMP is available before the machine is built only when QEMU was started with --preconfig. +Member 'coroutine' tells the QMP dispatcher whether the command handler +is safe to be run in a coroutine. It defaults to false. If it is true, +the command handler is called from coroutine context and may yield while +waiting for an external event (such as I/O completion) in order to avoid +blocking the guest and other background operations. + +It is an error to specify both 'coroutine': true and 'allow-oob': true +for a command. (We don't currently have a use case for both together and +without a use case, it's not entirely clear what the semantics should be.) + The optional 'if' member specifies a conditional. See "Configuring the schema" below for more on this.
include/qapi/qmp/dispatch.h +1 -0
@@ -24,6 +24,7 @@ typedef enum QmpCommandOptionsQCO_NO_SUCCESS_RESP = (1U <<0 ),QCO_ALLOW_OOB = (1U <<1 ),QCO_ALLOW_PRECONFIG = (1U <<2 ), +QCO_COROUTINE = (1U <<3 ), } QmpCommandOptions; typedef struct QmpCommand
tests/test-qmp-cmds.c +4 -0
@@ -35,6 +35,10 @@ void qmp_cmd_success_response(Error **errp) { } +void qmp_coroutine_cmd (Error **errp) +{ +} +Empty2 *qmp_user_def_cmd0 (Error **errp) {return g_new0 (Empty2,1 );
scripts/qapi/commands.py +7 -3
@@ -194,7 +194,8 @@ out: return ret -def gen_register_command(name, success_response, allow_oob, allow_preconfig): +def gen_register_command(name, success_response, allow_oob, allow_preconfig, + coroutine): options = [] if not success_response:
@@ -203,6 +204,8 @@ def gen_register_command(name, success_response, allow_oob, allow_preconfig): options += ['QCO_ALLOW_OOB'] if allow_preconfig: options += ['QCO_ALLOW_PRECONFIG'] + if coroutine: + options += ['QCO_COROUTINE'] if not options: options = ['QCO_NO_OPTIONS']
@@ -285,7 +288,7 @@ void %(c_prefix)sqmp_init_marshal(QmpCommandList *cmds); def visit_command(self, name, info, ifcond, arg_type, ret_type, gen, success_response, boxed, allow_oob, allow_preconfig, - features): + coroutine, features): if not gen: return # FIXME: If T is a user-defined type, the user is responsible
@@ -303,7 +306,8 @@ void %(c_prefix)sqmp_init_marshal(QmpCommandList *cmds); self._genh.add(gen_marshal_decl(name)) self._genc.add(gen_marshal(name, arg_type, boxed, ret_type)) self._regy.add(gen_register_command(name, success_response, - allow_oob, allow_preconfig)) + allow_oob, allow_preconfig, + coroutine)) def gen_commands(schema, output_dir, prefix):
scripts/qapi/doc.py +1 -1
@@ -264,7 +264,7 @@ class QAPISchemaGenDocVisitor(QAPISchemaVisitor): def visit_command(self, name, info, ifcond, arg_type, ret_type, gen, success_response, boxed, allow_oob, allow_preconfig, - features): + coroutine, features): doc = self.cur_doc self._gen.add(texi_msg('Command', doc, ifcond, texi_arguments(doc,
scripts/qapi/expr.py +8 -2
@@ -89,10 +89,16 @@ def check_flags(expr, info): if key in expr and expr[key] is not False: raise QAPISemError( info, "flag '%s' may only use false value" % key) - for key in ['boxed', 'allow-oob', 'allow-preconfig']: + for key in ['boxed', 'allow-oob', 'allow-preconfig', 'coroutine']: if key in expr and expr[key] is not True: raise QAPISemError( info, "flag '%s' may only use true value" % key) + if 'allow-oob' in expr and 'coroutine' in expr: + # This is not necessarily a fundamental incompatibility, but we don't + # have a use case and the desired semantics isn't obvious. The simplest + # solution is to forbid it until we get a use case for it. + raise QAPISemError(info, "flags 'allow-oob' and 'coroutine' " + "are incompatible") def check_if(expr, info, source):
@@ -344,7 +350,7 @@ def check_exprs(exprs): ['command'], ['data', 'returns', 'boxed', 'if', 'features', 'gen', 'success-response', 'allow-oob', - 'allow-preconfig']) + 'allow-preconfig', 'coroutine']) normalize_members(expr.get('data')) check_command(expr, info) elif meta == 'event':
scripts/qapi/introspect.py +1 -1
@@ -212,7 +212,7 @@ const QLitObject %(c_name)s = %(c_string)s; def visit_command(self, name, info, ifcond, arg_type, ret_type, gen, success_response, boxed, allow_oob, allow_preconfig, - features): + coroutine, features): arg_type = arg_type or self._schema.the_empty_object_type ret_type = ret_type or self._schema.the_empty_object_type obj = {'arg-type': self._use_type(arg_type),
scripts/qapi/schema.py +6 -3
@@ -128,7 +128,7 @@ class QAPISchemaVisitor(object): def visit_command(self, name, info, ifcond, arg_type, ret_type, gen, success_response, boxed, allow_oob, allow_preconfig, - features): + coroutine, features): pass def visit_event(self, name, info, ifcond, arg_type, boxed):
@@ -690,7 +690,7 @@ class QAPISchemaCommand(QAPISchemaEntity): def __init__(self, name, info, doc, ifcond, arg_type, ret_type, gen, success_response, boxed, allow_oob, allow_preconfig, - features): + coroutine, features): QAPISchemaEntity.__init__(self, name, info, doc, ifcond, features) assert not arg_type or isinstance(arg_type, str) assert not ret_type or isinstance(ret_type, str)
@@ -703,6 +703,7 @@ class QAPISchemaCommand(QAPISchemaEntity): self.boxed = boxed self.allow_oob = allow_oob self.allow_preconfig = allow_preconfig + self.coroutine = coroutine def check(self, schema): QAPISchemaEntity.check(self, schema)
@@ -745,7 +746,7 @@ class QAPISchemaCommand(QAPISchemaEntity): self.arg_type, self.ret_type, self.gen, self.success_response, self.boxed, self.allow_oob, - self.allow_preconfig, + self.allow_preconfig, self.coroutine, self.features)
@@ -1043,6 +1044,7 @@ class QAPISchema(object): boxed = expr.get('boxed', False) allow_oob = expr.get('allow-oob', False) allow_preconfig = expr.get('allow-preconfig', False) + coroutine = expr.get('coroutine', False) ifcond = expr.get('if') features = expr.get('features', []) if isinstance(data, OrderedDict):
@@ -1054,6 +1056,7 @@ class QAPISchema(object): self._def_entity(QAPISchemaCommand(name, info, doc, ifcond, data, rets, gen, success_response, boxed, allow_oob, allow_preconfig, + coroutine, self._make_features(features, info))) def _def_event(self, expr, info, doc):
tests/qapi-schema/test-qapi.py +4 -3
@@ -69,12 +69,13 @@ class QAPISchemaTestVisitor(QAPISchemaVisitor): def visit_command(self, name, info, ifcond, arg_type, ret_type, gen, success_response, boxed, allow_oob, allow_preconfig, - features): + coroutine, features): print('command %s %s -> %s' % (name, arg_type and arg_type.name, ret_type and ret_type.name)) - print(' gen=%s success_response=%s boxed=%s oob=%s preconfig=%s' - % (gen, success_response, boxed, allow_oob, allow_preconfig)) + print(' gen=%s success_response=%s boxed=%s oob=%s preconfig=%s%s' + % (gen, success_response, boxed, allow_oob, allow_preconfig, + " coroutine=True" if coroutine else "")) self._print_if(ifcond) self._print_features(features)
tests/Makefile.include +1 -0
@@ -286,6 +286,7 @@ qapi-schema += missing-type.json qapi-schema += nested-struct-data.json qapi-schema += nested-struct-data-invalid-dict.json qapi-schema += non-objects.json +qapi-schema += oob-coroutine.json qapi-schema += oob-test.json qapi-schema += allow-preconfig-test.json qapi-schema += pragma-doc-required-crap.json
tests/qapi-schema/oob-coroutine.err new file +2 -0
@@ -0,0 +1,2 @@ +oob-coroutine.json: In command 'oob-command-1': +oob-coroutine.json:2: flags 'allow-oob' and 'coroutine' are incompatible
tests/qapi-schema/oob-coroutine.json new file +2 -0
@@ -0,0 +1,2 @@ +# Check that incompatible flags allow-oob and coroutine are rejected +{ 'command': 'oob-command-1', 'allow-oob': true, 'coroutine': true }
tests/qapi-schema/oob-coroutine.out new file +0 -0
tests/qapi-schema/qapi-schema-test.json +1 -0
@@ -147,6 +147,7 @@ 'returns': 'UserDefTwo' } { 'command': 'cmd-success-response', 'data': {}, 'success-response': false } +{ 'command': 'coroutine-cmd', 'data': {}, 'coroutine': true } # Returning a non-dictionary requires a name from the whitelist { 'command': 'guest-get-time', 'data': {'a': 'int', '*b': 'int' },
tests/qapi-schema/qapi-schema-test.out +2 -0
@@ -203,6 +203,8 @@ command user_def_cmd2 q_obj_user_def_cmd2-arg -> UserDefTwo gen=True success_response=True boxed=False oob=False preconfig=False command cmd-success-response None -> None gen=True success_response=False boxed=False oob=False preconfig=False +command coroutine-cmd None -> None + gen=True success_response=True boxed=False oob=False preconfig=False coroutine=True object q_obj_guest-get-time-arg member a: int optional=False member b: int optional=True
Signature · 1 line
2.20.1
PATCH v5 2/4 vl: Initialise main loop earlier
In reply to Kevin WolfWe want to be able to use qemu_aio_context in the monitor initialisation.
--- vl.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
vl.c +5 -5
@@ -2894,6 +2894,11 @@ int main(int argc, char **argv, char **envp)runstate_init ();precopy_infrastructure_init ();postcopy_infrastructure_init (); + +if (qemu_init_main_loop (&main_loop_err)) { +error_report_err (main_loop_err); +exit (1 ); + }monitor_init_globals ();if (qcrypto_init (&err) <0 ) {
@@ -3811,11 +3816,6 @@ int main(int argc, char **argv, char **envp) qemu_unlink_pidfile_notifier.notify = qemu_unlink_pidfile;qemu_add_exit_notifier (&qemu_unlink_pidfile_notifier); -if (qemu_init_main_loop (&main_loop_err)) { -error_report_err (main_loop_err); -exit (1 ); - } -#ifdef CONFIG_SECCOMP olist =qemu_find_opts_err ("sandbox" ,NULL );if (olist) {
Signature · 1 line
2.20.1
PATCH v5 3/4 qmp: Move dispatcher to a coroutine
In reply to Kevin WolfThis moves the QMP dispatcher to a coroutine and runs all QMP command handlers that declare 'coroutine': true in coroutine context so they can avoid blocking the main loop while doing I/O or waiting for other events.
For commands that are not declared safe to run in a coroutine, the dispatcher drops out of coroutine context by calling the QMP command handler from a bottom half.
--- include/qapi/qmp/dispatch.h | 1 + monitor/monitor-internal.h | 6 +- monitor/monitor.c | 55 +++++++++++++--- monitor/qmp.c | 122 +++++++++++++++++++++++++++--------- qapi/qmp-dispatch.c | 44 ++++++++++++- qapi/qmp-registry.c | 3 + util/aio-posix.c | 7 ++- 7 files changed, 196 insertions(+), 42 deletions(-)
include/qapi/qmp/dispatch.h +1 -0
@@ -30,6 +30,7 @@ typedef enum QmpCommandOptions typedef struct QmpCommand { const char *name; + /* Runs in coroutine context if QCO_COROUTINE is set */ QmpCommandFunc *fn; QmpCommandOptions options; QTAILQ_ENTRY(QmpCommand) node;
monitor/monitor-internal.h +4 -2
@@ -155,7 +155,9 @@ static inline bool monitor_is_qmp(const Monitor *mon) typedef QTAILQ_HEAD(MonitorList, Monitor) MonitorList;extern IOThread *mon_iothread; -extern QEMUBH *qmp_dispatcher_bh; +extern Coroutine *qmp_dispatcher_co; +extern bool qmp_dispatcher_co_shutdown; +extern bool qmp_dispatcher_co_busy;extern QmpCommandList qmp_commands, qmp_cap_negotiation_commands;extern QemuMutex monitor_lock;extern MonitorList mon_list;
@@ -173,7 +175,7 @@ void monitor_fdsets_cleanup(void);void qmp_send_response (MonitorQMP *mon,const QDict *rsp);void monitor_data_destroy_qmp (MonitorQMP *mon); -void monitor_qmp_bh_dispatcher (void *data); +void coroutine_fn monitor_qmp_dispatcher_co(void *data);int get_monitor_def (int64_t *pval,const char *name);void help_cmd (Monitor *mon,const char *name);
monitor/monitor.c +47 -8
73 lines not on this page · raw message
monitor/qmp.c +92 -30
148 lines not on this page · raw message
qapi/qmp-dispatch.c +43 -1
74 lines not on this page · raw message
qapi/qmp-registry.c +3 -0
@@ -20,6 +20,9 @@ void qmp_register_command(QmpCommandList *cmds, const char *name, {QmpCommand *cmd =g_malloc0 (sizeof (*cmd)); +/* QCO_COROUTINE and QCO_ALLOW_OOB are incompatible for now */ +assert (!((options &QCO_COROUTINE ) && (options &QCO_ALLOW_OOB ))); + cmd->name = name; cmd->fn = fn; cmd->enabled = true;
util/aio-posix.c +6 -1
@@ -15,6 +15,7 @@#include "qemu/osdep.h" #include "block/block.h" +#include "qemu/main-loop.h" #include "qemu/rcu_queue.h" #include "qemu/sockets.h" #include "qemu/cutils.h"
@@ -616,7 +617,11 @@ bool aio_poll(AioContext *ctx, bool blocking)int64_t timeout;int64_t start =0 ; -assert (in_aio_context_home_thread (ctx)); +/* aio_poll() may only be called in the AioContext's thread. iohandler_ctx +* is special in that it runs in the main thread, but that thread's context +* is qemu_aio_context. */ +assert (in_aio_context_home_thread (ctx ==iohandler_get_aio_context () ? +qemu_get_aio_context () : ctx));/* aio_notify can avoid the expensive event_notifier_set if * everything (file descriptors, bottom halves, timers) will
Signature · 1 line
2.20.1
PATCH v5 4/4 block: Mark 'block_resize' as coroutine
In reply to Kevin Wolfblock_resize is safe to run in a coroutine, and it does some I/O that could potentially take quite some time, so use it as an example for the new 'coroutine': true annotation in the QAPI schema.
--- qapi/block-core.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
qapi/block-core.json +2 -1
@@ -1344,7 +1344,8 @@ { 'command': 'block_resize', 'data': { '*device': 'str', '*node-name': 'str', - 'size': 'int' } } + 'size': 'int' }, + 'coroutine': true } ## # @NewImageMode:
Signature · 1 line
2.20.1
Re: [PATCH v5 2/4] vl: Initialise main loop earlier
In reply to Kevin WolfQuoted 15 lines · Kevin Wolf
We want to be able to use
qemu_aio_contextin the monitor initialisation.Signed-off-by Kevin Wolf <[email protected]>Reviewed-by Marc-André Lureau <[email protected]>Reviewed-by Markus Armbruster <[email protected]>--- vl.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)vl.c +0
-0
vl.c int main(int argc, char **argv, char **envp) · line 2902
Quoted 9 lines
vl.c +5
-0@@ -2894,6 +2894,11 @@ int main(int argc, char **argv, char **envp)runstate_init ();precopy_infrastructure_init ();postcopy_infrastructure_init (); + +if (qemu_init_main_loop (&main_loop_err)) { +error_report_err (main_loop_err); +exit (1 ); + }monitor_init_globals ();
This is a tiny bit scary, as we now have around 1kloc of code between here and os_daemonize() where in the future we may accidentally cause the aio context's on-demand thread pool to spawn before fork()ing (silently losing the threads again - we did have such an issue right there in monitor_init_globals() in the past)
For *now* it should be fine since currently that wouldn't have worked, but we may need to keep an eye out for that in future patches. Basically, not everything we do between here and os_daemonize() way down below is actually allowed to freely use the main loop's aio context even if now it already exists from this point onward.
I wonder if aio_get_thread_pool() should check the daemonization state (maybe with some debug #ifdef)?
Quoted 16 lines
vl.c +0
-5if (qcrypto_init (&err) <0 ) {@@ -3811,11 +3816,6 @@ int main(int argc, char **argv, char **envp) qemu_unlink_pidfile_notifier.notify = qemu_unlink_pidfile;qemu_add_exit_notifier (&qemu_unlink_pidfile_notifier); -if (qemu_init_main_loop (&main_loop_err)) { -error_report_err (main_loop_err); -exit (1 ); - } -#ifdef CONFIG_SECCOMP olist =qemu_find_opts_err ("sandbox" ,NULL );if (olist) {Signature · 1 line
2.20.1
Re: [PATCH v5 2/4] vl: Initialise main loop earlier
Am 19.02.2020 um 15:07 hat Wolfgang Bumiller geschrieben:
Quoted 23 lines · Kevin Wolf
Quoted 22 lines
We want to be able to use
qemu_aio_contextin the monitor initialisation.Signed-off-by Kevin Wolf <[email protected]>Reviewed-by Marc-André Lureau <[email protected]>Reviewed-by Markus Armbruster <[email protected]>--- vl.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)vl.c +4
-0@@ -2894,6 +2894,11 @@ int main(int argc, char **argv, char **envp)runstate_init ();precopy_infrastructure_init ();postcopy_infrastructure_init (); + +if (qemu_init_main_loop (&main_loop_err)) { +error_report_err (main_loop_err); +exit (1 );
Quoted 8 lines
vl.c int main(int argc, char **argv, char **envp) · line 2902
Quoted 2 lines
vl.c +1
-0+ }monitor_init_globals ();This is a tiny bit scary, as we now have around 1kloc of code between here and
os_daemonize()where in the future we may accidentally cause the aio context's on-demand thread pool to spawn before fork()ing (silently losing the threads again - we did have such an issue right there inmonitor_init_globals()in the past)
I don't think it's that bad, because while it is many lines, it's just boring option parsing code. I certainly don't think it's likely to start using a thread pool anywhere.
However, I also wonder now if this patch is actually necessary. Maybe some intermediate version of the series actually used qemu_aio_context in monitor_init_globals_core(), but none of the versions actually sent to the list do. They all use iohandler_get_aio_context(), which should be safe before the main loop is initialised. To make sure that I didn't miss anything, 'make check' passes without the patch.
So maybe we can just drop this patch after all.
Kevin
Re: [PATCH v5 1/4] qapi: Add a 'coroutine' flag for commands
In reply to Kevin WolfQuoted 47 lines · Kevin Wolf
This patch adds a new 'coroutine' flag to QMP command definitions that tells the QMP dispatcher that the command handler is safe to be run in a coroutine.
The documentation of the new flag pretends that this flag is already used as intended, which it isn't yet after this patch. We'll implement this in another patch in this series.
Signed-off-by Kevin Wolf <[email protected]>Reviewed-by Marc-André Lureau <[email protected]>Reviewed-by Markus Armbruster <[email protected]>--- docs/devel/qapi-code-gen.txt | 11 +++++++++++ include/qapi/qmp/dispatch.h | 1 + tests/test-qmp-cmds.c | 4 ++++ scripts/qapi/commands.py | 10 +++++++--- scripts/qapi/doc.py | 2 +- scripts/qapi/expr.py | 10 ++++++++-- scripts/qapi/introspect.py | 2 +- scripts/qapi/schema.py | 9 ++++++--- tests/qapi-schema/test-qapi.py | 7 ++++--- tests/Makefile.include | 1 + tests/qapi-schema/oob-coroutine.err | 2 ++ tests/qapi-schema/oob-coroutine.json | 2 ++ tests/qapi-schema/oob-coroutine.out | 0 tests/qapi-schema/qapi-schema-test.json | 1 + tests/qapi-schema/qapi-schema-test.out | 2 ++ 15 files changed, 51 insertions(+), 13 deletions(-) create mode 100644 tests/qapi-schema/oob-coroutine.err create mode 100644 tests/qapi-schema/oob-coroutine.json create mode 100644 tests/qapi-schema/oob-coroutine.outdocs/devel/qapi-code-gen.txt +1
-0@@ -457,6 +457,7 @@ Syntax: '*gen': false, '*allow-oob': true, '*allow-preconfig': true, + '*coroutine': true, '*if': COND, '*features': FEATURES }@@ -581,6 +582,16 @@ before the machine is built. It defaults to false. For example: QMP is available before the machine is built only when QEMU was started with --preconfig.
docs/devel/qapi-code-gen.txt before the machine is built. It defaults to false. For example: · line 593
Quoted 10 lines
docs/devel/qapi-code-gen.txt +9
-0+Member 'coroutine' tells the QMP dispatcher whether the command handler +is safe to be run in a coroutine. It defaults to false. If it is true, +the command handler is called from coroutine context and may yield while +waiting for an external event (such as I/O completion) in order to avoid +blocking the guest and other background operations. + +It is an error to specify both 'coroutine': true and 'allow-oob': true +for a command. (We don't currently have a use case for both together and +without a use case, it's not entirely clear what the semantics should be.)
The parenthesis is new since v4. I like its contents. I'm not fond of putting complete sentences in parenthesis. I'll drop them, if you don't mind.
Quoted 4 lines
docs/devel/qapi-code-gen.txt +1
-0+ The optional 'if' member specifies a conditional. See "Configuring the schema" below for more on this.
[...]
Quoted 7 lines
scripts/qapi/expr.py +0
-0@@ -89,10 +89,16 @@ def check_flags(expr, info): if key in expr and expr[key] is not False: raise QAPISemError(
scripts/qapi/expr.py def check_flags(expr, info): · line 99
Quoted 10 lines
scripts/qapi/expr.py +5
-1info, "flag '%s' may only use false value" % key) - for key in ['boxed', 'allow-oob', 'allow-preconfig']: + for key in ['boxed', 'allow-oob', 'allow-preconfig', 'coroutine']: if key in expr and expr[key] is not True: raise QAPISemError( info, "flag '%s' may only use true value" % key) + if 'allow-oob' in expr and 'coroutine' in expr: + # This is not necessarily a fundamental incompatibility, but we don't + # have a use case and the desired semantics isn't obvious. The simplest + # solution is to forbid it until we get a use case for it.
Appreciated. I'll word-wrap, if you don't mind.
Quoted 6 lines
scripts/qapi/expr.py +2
-0+ raise QAPISemError(info, "flags 'allow-oob' and 'coroutine' " + "are incompatible") def check_if(expr, info, source):
scripts/qapi/expr.py def check_exprs(exprs): · line 356
Quoted 8 lines
scripts/qapi/expr.py +1
-1@@ -344,7 +350,7 @@ def check_exprs(exprs): ['command'], ['data', 'returns', 'boxed', 'if', 'features', 'gen', 'success-response', 'allow-oob', - 'allow-preconfig']) + 'allow-preconfig', 'coroutine']) normalize_members(expr.get('data')) check_command(expr, info) elif meta == 'event':
[...]
R-by stands.
Re: [PATCH v5 3/4] qmp: Move dispatcher to a coroutine
In reply to Kevin WolfQuoted 75 lines · Kevin Wolf
This moves the QMP dispatcher to a coroutine and runs all QMP command handlers that declare 'coroutine': true in coroutine context so they can avoid blocking the main loop while doing I/O or waiting for other events.
For commands that are not declared safe to run in a coroutine, the dispatcher drops out of coroutine context by calling the QMP command handler from a bottom half.
Signed-off-by Kevin Wolf <[email protected]>--- include/qapi/qmp/dispatch.h | 1 + monitor/monitor-internal.h | 6 +- monitor/monitor.c | 55 +++++++++++++--- monitor/qmp.c | 122 +++++++++++++++++++++++++++--------- qapi/qmp-dispatch.c | 44 ++++++++++++- qapi/qmp-registry.c | 3 + util/aio-posix.c | 7 ++- 7 files changed, 196 insertions(+), 42 deletions(-)include/qapi/qmp/dispatch.h +1
-0@@ -30,6 +30,7 @@ typedef enum QmpCommandOptions typedef struct QmpCommand { const char *name; + /* Runs in coroutine context if QCO_COROUTINE is set */ QmpCommandFunc *fn; QmpCommandOptions options; QTAILQ_ENTRY(QmpCommand) node;monitor/monitor-internal.h +4
-2@@ -155,7 +155,9 @@ static inline bool monitor_is_qmp(const Monitor *mon) typedef QTAILQ_HEAD(MonitorList, Monitor) MonitorList;extern IOThread *mon_iothread; -extern QEMUBH *qmp_dispatcher_bh; +extern Coroutine *qmp_dispatcher_co; +extern bool qmp_dispatcher_co_shutdown; +extern bool qmp_dispatcher_co_busy;extern QmpCommandList qmp_commands, qmp_cap_negotiation_commands;extern QemuMutex monitor_lock;extern MonitorList mon_list;@@ -173,7 +175,7 @@ void monitor_fdsets_cleanup(void);void qmp_send_response (MonitorQMP *mon,const QDict *rsp);void monitor_data_destroy_qmp (MonitorQMP *mon); -void monitor_qmp_bh_dispatcher (void *data); +void coroutine_fn monitor_qmp_dispatcher_co(void *data);int get_monitor_def (int64_t *pval,const char *name);void help_cmd (Monitor *mon,const char *name);monitor/monitor.c +9
-2@@ -53,8 +53,32 @@ typedef struct {/* Shared monitor I/O thread */ IOThread *mon_iothread; -/* Bottom half to dispatch the requests received from I/O thread */ -QEMUBH *qmp_dispatcher_bh; +/* Coroutine to dispatch the requests received from I/O thread */ +Coroutine *qmp_dispatcher_co; + +/* Set to true when the dispatcher coroutine should terminate */ +bool qmp_dispatcher_co_shutdown; + +/* +* qmp_dispatcher_co_busy is used for synchronisation between the +* monitor thread and the main thread to ensure that the dispatcher
monitor/monitor.c typedef struct { · line 74
Quoted 10 lines
monitor/monitor.c +10
-0+* coroutine never gets scheduled a second time when it's already +* scheduled (scheduling the same coroutine twice is forbidden). +* +* It is true if the coroutine is active and processing requests. +* Additional requests may then be pushed onto a mon->qmp_requests, +* and @qmp_dispatcher_co_shutdown may be set without further ado. +* @qmp_dispatcher_co_busy must not be woken up in this case. +* +* If false, you also have to set @qmp_dispatcher_co_busy to true and +* wake up @qmp_dispatcher_co after pushing the new requests.
Also after setting @qmp_dispatcher_co_shutdown, right?
Happy to tweak the comment without a respin.
Quoted 10 lines
monitor/monitor.c +7
-0+* +* The coroutine will automatically change this variable back to false +* before it yields. Nobody else may set the variable to false. +* +* Access must be atomic for thread safety. +*/ +bool qmp_dispatcher_co_busy;/* Protects mon_list, monitor_qapi_event_state, monitor_destroyed. */ QemuMutex monitor_lock;
[...]
Re: [PATCH v5 3/4] qmp: Move dispatcher to a coroutine
Am 03.03.2020 um 09:49 hat Markus Armbruster geschrieben:
Quoted 90 lines
Quoted 75 lines · Kevin Wolf
This moves the QMP dispatcher to a coroutine and runs all QMP command handlers that declare 'coroutine': true in coroutine context so they can avoid blocking the main loop while doing I/O or waiting for other events.
For commands that are not declared safe to run in a coroutine, the dispatcher drops out of coroutine context by calling the QMP command handler from a bottom half.
Signed-off-by Kevin Wolf <[email protected]>--- include/qapi/qmp/dispatch.h | 1 + monitor/monitor-internal.h | 6 +- monitor/monitor.c | 55 +++++++++++++--- monitor/qmp.c | 122 +++++++++++++++++++++++++++--------- qapi/qmp-dispatch.c | 44 ++++++++++++- qapi/qmp-registry.c | 3 + util/aio-posix.c | 7 ++- 7 files changed, 196 insertions(+), 42 deletions(-)include/qapi/qmp/dispatch.h +1
-0@@ -30,6 +30,7 @@ typedef enum QmpCommandOptions typedef struct QmpCommand { const char *name; + /* Runs in coroutine context if QCO_COROUTINE is set */ QmpCommandFunc *fn; QmpCommandOptions options; QTAILQ_ENTRY(QmpCommand) node;monitor/monitor-internal.h +4
-2@@ -155,7 +155,9 @@ static inline bool monitor_is_qmp(const Monitor *mon) typedef QTAILQ_HEAD(MonitorList, Monitor) MonitorList;extern IOThread *mon_iothread; -extern QEMUBH *qmp_dispatcher_bh; +extern Coroutine *qmp_dispatcher_co; +extern bool qmp_dispatcher_co_shutdown; +extern bool qmp_dispatcher_co_busy;extern QmpCommandList qmp_commands, qmp_cap_negotiation_commands;extern QemuMutex monitor_lock;extern MonitorList mon_list;@@ -173,7 +175,7 @@ void monitor_fdsets_cleanup(void);void qmp_send_response (MonitorQMP *mon,const QDict *rsp);void monitor_data_destroy_qmp (MonitorQMP *mon); -void monitor_qmp_bh_dispatcher (void *data); +void coroutine_fn monitor_qmp_dispatcher_co(void *data);int get_monitor_def (int64_t *pval,const char *name);void help_cmd (Monitor *mon,const char *name);monitor/monitor.c +9
-2@@ -53,8 +53,32 @@ typedef struct {/* Shared monitor I/O thread */ IOThread *mon_iothread; -/* Bottom half to dispatch the requests received from I/O thread */ -QEMUBH *qmp_dispatcher_bh; +/* Coroutine to dispatch the requests received from I/O thread */ +Coroutine *qmp_dispatcher_co; + +/* Set to true when the dispatcher coroutine should terminate */ +bool qmp_dispatcher_co_shutdown; + +/* +* qmp_dispatcher_co_busy is used for synchronisation between the +* monitor thread and the main thread to ensure that the dispatcher monitor/monitor.c typedef struct { · line 74
Quoted 10 lines
monitor/monitor.c +10
-0+* coroutine never gets scheduled a second time when it's already +* scheduled (scheduling the same coroutine twice is forbidden). +* +* It is true if the coroutine is active and processing requests. +* Additional requests may then be pushed onto a mon->qmp_requests, +* and @qmp_dispatcher_co_shutdown may be set without further ado. +* @qmp_dispatcher_co_busy must not be woken up in this case. +* +* If false, you also have to set @qmp_dispatcher_co_busy to true and +* wake up @qmp_dispatcher_co after pushing the new requests. Also after setting @qmp_dispatcher_co_shutdown, right?
Quoted 1 line
Happy to tweak the comment without a respin.
I understood a shutdown request as just another kind of request, but if you want the comment to be more detailed, feel free.
Kevin
Re: [PATCH v5 1/4] qapi: Add a 'coroutine' flag for commands
In reply to Markus ArmbrusterAm 03.03.2020 um 09:10 hat Markus Armbruster geschrieben:
Quoted 50 lines
Quoted 48 lines · Kevin Wolf
This patch adds a new 'coroutine' flag to QMP command definitions that tells the QMP dispatcher that the command handler is safe to be run in a coroutine.
The documentation of the new flag pretends that this flag is already used as intended, which it isn't yet after this patch. We'll implement this in another patch in this series.
Signed-off-by Kevin Wolf <[email protected]>Reviewed-by Marc-André Lureau <[email protected]>Reviewed-by Markus Armbruster <[email protected]>--- docs/devel/qapi-code-gen.txt | 11 +++++++++++ include/qapi/qmp/dispatch.h | 1 + tests/test-qmp-cmds.c | 4 ++++ scripts/qapi/commands.py | 10 +++++++--- scripts/qapi/doc.py | 2 +- scripts/qapi/expr.py | 10 ++++++++-- scripts/qapi/introspect.py | 2 +- scripts/qapi/schema.py | 9 ++++++--- tests/qapi-schema/test-qapi.py | 7 ++++--- tests/Makefile.include | 1 + tests/qapi-schema/oob-coroutine.err | 2 ++ tests/qapi-schema/oob-coroutine.json | 2 ++ tests/qapi-schema/oob-coroutine.out | 0 tests/qapi-schema/qapi-schema-test.json | 1 + tests/qapi-schema/qapi-schema-test.out | 2 ++ 15 files changed, 51 insertions(+), 13 deletions(-) create mode 100644 tests/qapi-schema/oob-coroutine.err create mode 100644 tests/qapi-schema/oob-coroutine.json create mode 100644 tests/qapi-schema/oob-coroutine.outdocs/devel/qapi-code-gen.txt +1
-0@@ -457,6 +457,7 @@ Syntax: '*gen': false, '*allow-oob': true, '*allow-preconfig': true, + '*coroutine': true, '*if': COND, '*features': FEATURES }@@ -581,6 +582,16 @@ before the machine is built. It defaults to false. For example: QMP is available before the machine is built only when QEMU was started with --preconfig.
Quoted 13 lines
docs/devel/qapi-code-gen.txt before the machine is built. It defaults to false. For example: · line 593
Quoted 9 lines
docs/devel/qapi-code-gen.txt +9
-0+Member 'coroutine' tells the QMP dispatcher whether the command handler +is safe to be run in a coroutine. It defaults to false. If it is true, +the command handler is called from coroutine context and may yield while +waiting for an external event (such as I/O completion) in order to avoid +blocking the guest and other background operations. + +It is an error to specify both 'coroutine': true and 'allow-oob': true +for a command. (We don't currently have a use case for both together and +without a use case, it's not entirely clear what the semantics should be.)The parenthesis is new since v4. I like its contents. I'm not fond of putting complete sentences in parenthesis. I'll drop them, if you don't mind.
You asked this already in the discussion for v4. Yes, I still agree.
Quoted 16 lines
Quoted 4 lines
docs/devel/qapi-code-gen.txt +1
-0+ The optional 'if' member specifies a conditional. See "Configuring the schema" below for more on this.[...]
Quoted 11 lines
scripts/qapi/expr.py +1
-1@@ -89,10 +89,16 @@ def check_flags(expr, info): if key in expr and expr[key] is not False: raise QAPISemError( info, "flag '%s' may only use false value" % key) - for key in ['boxed', 'allow-oob', 'allow-preconfig']: + for key in ['boxed', 'allow-oob', 'allow-preconfig', 'coroutine']: if key in expr and expr[key] is not True:
Quoted 8 lines
scripts/qapi/expr.py def check_flags(expr, info): · line 99
Quoted 6 lines
scripts/qapi/expr.py +4
-0raise QAPISemError( info, "flag '%s' may only use true value" % key) + if 'allow-oob' in expr and 'coroutine' in expr: + # This is not necessarily a fundamental incompatibility, but we don't + # have a use case and the desired semantics isn't obvious. The simplest + # solution is to forbid it until we get a use case for it.Appreciated. I'll word-wrap, if you don't mind.
I still don't agree with comment line width being smaller than code line width, and think it's in disagreement with CODING_STYLE, but if you can't help it, adjust the formatting however you like.
Quoted 16 lines
Quoted 14 lines
scripts/qapi/expr.py +3
-1+ raise QAPISemError(info, "flags 'allow-oob' and 'coroutine' " + "are incompatible") def check_if(expr, info, source):@@ -344,7 +350,7 @@ def check_exprs(exprs): ['command'], ['data', 'returns', 'boxed', 'if', 'features', 'gen', 'success-response', 'allow-oob', - 'allow-preconfig']) + 'allow-preconfig', 'coroutine']) normalize_members(expr.get('data')) check_command(expr, info) elif meta == 'event':[...]
Quoted 1 line
R-by stands.
Kevin
Markus Armbruster
AppliedLooks like PATCH 2 isn't necessary anymore, and PATCH 4 needs a respin. I tentatively queued PATCH 1+3, in the hope of getting either PATCH 4 or Marc-André's screendump patch in time for 5.0.
Pushed to branch monitor-next in git://repo.or.cz/qemu/armbru.git.
Appears to be down right now.
Thanks!
Re: [PATCH v5 3/4] qmp: Move dispatcher to a coroutine
In reply to Kevin WolfQuoted 10 lines · Kevin Wolf
This moves the QMP dispatcher to a coroutine and runs all QMP command handlers that declare 'coroutine': true in coroutine context so they can avoid blocking the main loop while doing I/O or waiting for other events.
For commands that are not declared safe to run in a coroutine, the dispatcher drops out of coroutine context by calling the QMP command handler from a bottom half.
Signed-off-by Kevin Wolf <[email protected]>
Uh, what about @cur_mon?
@cur_mon points to the current monitor while a command executes. Initial value is null. It is set in three places (not counting unit tests), and all three save, set, do something that may use @cur_mon, restore:
* monitor_qmp_dispatch(), for use within qmp_dispatch()
* monitor_read(), for use within handle_hmp_command()
* qmp_human_monitor_command(), also for use within handle_hmp_command()
Therefore, @cur_mon is null unless we're running within qmp_dispatch() or handle_hmp_command().
Example of use: error_report() & friends print "to current monitor if we have one, else to stderr." Makes sharing code between HMP and CLI easier. Uses @cur_mon under the hood.
@cur_mon is thread-local.
I'm afraid we have to save, clear and restore @cur_mon around a yield.
Re: [PATCH v5 3/4] qmp: Move dispatcher to a coroutine
Am 18.03.2020 um 16:36 hat Markus Armbruster geschrieben:
Quoted 20 lines
Quoted 10 lines · Kevin Wolf
This moves the QMP dispatcher to a coroutine and runs all QMP command handlers that declare 'coroutine': true in coroutine context so they can avoid blocking the main loop while doing I/O or waiting for other events.
For commands that are not declared safe to run in a coroutine, the dispatcher drops out of coroutine context by calling the QMP command handler from a bottom half.
Signed-off-by Kevin Wolf <[email protected]>Uh, what about @cur_mon?
@cur_mon points to the current monitor while a command executes. Initial value is null. It is set in three places (not counting unit tests), and all three save, set, do something that may use @cur_mon, restore:
Quoted 6 lines
*
monitor_qmp_dispatch(), for use withinqmp_dispatch()
*monitor_read(), for use withinhandle_hmp_command()
*qmp_human_monitor_command(), also for use withinhandle_hmp_command()Therefore, @cur_mon is null unless we're running within
qmp_dispatch()orhandle_hmp_command().
Can we make it NULL for coroutine-enabled handlers?
Quoted 3 lines
Example of use:
error_report()& friends print "to current monitor if we have one, else to stderr." Makes sharing code between HMP and CLI easier. Uses @cur_mon under the hood.
error_report() eventually prints to stderr both for cur_mon == NULL and for QMP monitors. Is there an important difference between both cases?
There is error_vprintf_unless_qmp(), which behaves differently for both cases. However, it is only used in VNC code, so that code would have to keep coroutines disabled.
Is cur_mon used much in other functions called by QMP handlers?
Quoted 3 lines
@cur_mon is thread-local.
I'm afraid we have to save, clear and restore @cur_mon around a yield.
That sounds painful enough that I'd rather avoid it.
Kevin
Re: [PATCH v5 3/4] qmp: Move dispatcher to a coroutine
Hi
Quoted 22 lines · Kevin Wolf
Am 18.03.2020 um 16:36 hat Markus Armbruster geschrieben:
Quoted 20 lines
Quoted 10 lines · Kevin Wolf
This moves the QMP dispatcher to a coroutine and runs all QMP command handlers that declare 'coroutine': true in coroutine context so they can avoid blocking the main loop while doing I/O or waiting for other events.
For commands that are not declared safe to run in a coroutine, the dispatcher drops out of coroutine context by calling the QMP command handler from a bottom half.
Signed-off-by Kevin Wolf <[email protected]>Uh, what about @cur_mon?
@cur_mon points to the current monitor while a command executes. Initial value is null. It is set in three places (not counting unit tests), and all three save, set, do something that may use @cur_mon, restore:
Quoted 8 lines
Quoted 6 lines
*
monitor_qmp_dispatch(), for use withinqmp_dispatch()
*monitor_read(), for use withinhandle_hmp_command()
*qmp_human_monitor_command(), also for use withinhandle_hmp_command()Therefore, @cur_mon is null unless we're running within
qmp_dispatch()orhandle_hmp_command().Can we make it NULL for coroutine-enabled handlers?
fwiw, I think /dev/fdset doesn't care about cur_mon. However, qmp handlers that use monitor_get_fd() usually depend on cur_mon.
Note: I wonder if add-fd (fdsets) and getfd (monitor fds) deserve to co-exist.
Quoted 22 lines
Quoted 4 lines
Example of use:
error_report()& friends print "to current monitor if we have one, else to stderr." Makes sharing code between HMP and CLI easier. Uses @cur_mon under the hood.
error_report()eventually prints to stderr both forcur_mon== NULL and for QMP monitors. Is there an important difference between both cases?There is
error_vprintf_unless_qmp(), which behaves differently for both cases. However, it is only used in VNC code, so that code would have to keep coroutines disabled.Is
cur_monused much in other functions called by QMP handlers?Quoted 3 lines
@cur_mon is thread-local.
I'm afraid we have to save, clear and restore @cur_mon around a yield.
That sounds painful enough that I'd rather avoid it.
Kevin
Signature · 1 line
Marc-André Lureau
Markus Armbruster
Reviewed-by Paolo BonziniRe: [PATCH v5 3/4] qmp: Move dispatcher to a coroutine
In reply to Kevin WolfQuoted 21 lines · Kevin Wolf
Am 18.03.2020 um 16:36 hat Markus Armbruster geschrieben:
Quoted 20 lines
Quoted 10 lines · Kevin Wolf
This moves the QMP dispatcher to a coroutine and runs all QMP command handlers that declare 'coroutine': true in coroutine context so they can avoid blocking the main loop while doing I/O or waiting for other events.
For commands that are not declared safe to run in a coroutine, the dispatcher drops out of coroutine context by calling the QMP command handler from a bottom half.
Signed-off-by Kevin Wolf <[email protected]>Uh, what about @cur_mon?
@cur_mon points to the current monitor while a command executes. Initial value is null. It is set in three places (not counting unit tests), and all three save, set, do something that may use @cur_mon, restore:
Quoted 8 lines
Quoted 6 lines
*
monitor_qmp_dispatch(), for use withinqmp_dispatch()
*monitor_read(), for use withinhandle_hmp_command()
*qmp_human_monitor_command(), also for use withinhandle_hmp_command()Therefore, @cur_mon is null unless we're running within
qmp_dispatch()orhandle_hmp_command().Can we make it NULL for coroutine-enabled handlers?
Sets up and arms a bear trap, I'm afraid.
We can rely on code review to ensure a handler we want to coroutine-enable does not access @cur_mon. But how can we ensure no uses creep back? Not even on error paths, where testing tends to be ineffective?
@cur_mon goes back to Jan's commit 376253ece48 (March 2009). Meant to be merely a stop gap:
For the case that monitor outputs so far happen without clearly identifiable context, the global variable cur_mon is introduced that shall once provide a pointer either to the current active monitor (while processing commands) or to the default one. On the mid or long term, those use case will be obsoleted so that this variable can be removed again.
It's been eleven years, and we haven't really gotten closer to getting them "obsoleted". I can't stop you if you want to try. Myself, I'd rather give up and eliminate the Monitor * parameter passing.
Quoted 6 lines
Quoted 3 lines
Example of use:
error_report()& friends print "to current monitor if we have one, else to stderr." Makes sharing code between HMP and CLI easier. Uses @cur_mon under the hood.
error_report()eventually prints to stderr both forcur_mon== NULL and for QMP monitors. Is there an important difference between both cases?
This goes back to
commit 4ad417baa43424b6b988c52b83989fd95670c113
Author: Cole Robinson <[email protected]> Date: Fri Mar 21 19:42:24 2014 -0400
error: Print error_report() to stderr if using qmp
monitor_printf will drop the requested output if cur_mon is qmp (for good reason). However these messages are often helpful for debugging issues with via libvirt.
If we know the message won't hit the monitor, send it to stderr.
Use of error_report() in QMP context is wrong more often than not. Still, spewing the message to stderr is less bad than throwing it away.
Quoted 3 lines
There is
error_vprintf_unless_qmp(), which behaves differently for both cases. However, it is only used in VNC code, so that code would have to keep coroutines disabled.
It has seen other users over the years.
error_printf_unless_qmp() is a convenient way to print hints for humans. In HMP context, you reach the human by printing to @cur_mon. Outside monitor context, you reach the human by printing to stdout or stderr. In QMP context, we're talking to a machine.
Quoted 1 line
Is
cur_monused much in other functions called by QMP handlers?
Marc-André pointed to the file-descriptor passing stuff.
To be sure that's all, we'd have to review all uses of @cur_mon.
Quoted 5 lines
Quoted 3 lines
@cur_mon is thread-local.
I'm afraid we have to save, clear and restore @cur_mon around a yield.
That sounds painful enough that I'd rather avoid it.
I've seen coroutine implementations for C that provide coroutine-local variables of sorts by managing a thread-local opaque pointer.
Re: [PATCH v5 3/4] qmp: Move dispatcher to a coroutine
In reply to Marc-André LureauQuoted 32 lines · Marc-André Lureau
Hi
Quoted 29 lines · Kevin Wolf
Am 18.03.2020 um 16:36 hat Markus Armbruster geschrieben:
Quoted 26 lines
Quoted 10 lines · Kevin Wolf
This moves the QMP dispatcher to a coroutine and runs all QMP command handlers that declare 'coroutine': true in coroutine context so they can avoid blocking the main loop while doing I/O or waiting for other events.
For commands that are not declared safe to run in a coroutine, the dispatcher drops out of coroutine context by calling the QMP command handler from a bottom half.
Signed-off-by Kevin Wolf <[email protected]>Uh, what about @cur_mon?
@cur_mon points to the current monitor while a command executes. Initial value is null. It is set in three places (not counting unit tests), and all three save, set, do something that may use @cur_mon, restore:
*
monitor_qmp_dispatch(), for use withinqmp_dispatch()
*monitor_read(), for use withinhandle_hmp_command()
*qmp_human_monitor_command(), also for use withinhandle_hmp_command()Therefore, @cur_mon is null unless we're running within
qmp_dispatch()orhandle_hmp_command().
Quoted 6 lines
Quoted 1 line
Can we make it NULL for coroutine-enabled handlers?
fwiw, I think
/dev/fdsetdoesn't care aboutcur_mon. However, qmp handlers that usemonitor_get_fd()usually depend oncur_mon.Note: I wonder if add-fd (fdsets) and getfd (monitor fds) deserve to co-exist.
Beats me.
If one of them is more general, we could consider deprecating the other one.