From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: stefanha@redhat.com, marcandre.lureau@gmail.com,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
dgilbert@redhat.com
Subject: Re: [PATCH v7 06/13] qmp: Call monitor_set_cur() only in qmp_dispatch()
Date: Fri, 25 Sep 2020 17:13:04 +0200 [thread overview]
Message-ID: <20200925151304.GE5731@linux.fritz.box> (raw)
In-Reply-To: <877dswo0mf.fsf@dusky.pond.sub.org>
Am 14.09.2020 um 17:10 hat Markus Armbruster geschrieben:
> Kevin Wolf <kwolf@redhat.com> writes:
>
> > The correct way to set the current monitor for a coroutine handler will
> > be different than for a blocking handler, so monitor_set_cur() needs to
> > be called in qmp_dispatch().
> >
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > ---
> > include/qapi/qmp/dispatch.h | 3 ++-
> > monitor/qmp.c | 8 +-------
> > qapi/qmp-dispatch.c | 8 +++++++-
> > qga/main.c | 2 +-
> > stubs/monitor-core.c | 5 +++++
> > tests/test-qmp-cmds.c | 6 +++---
> > 6 files changed, 19 insertions(+), 13 deletions(-)
> >
> > diff --git a/include/qapi/qmp/dispatch.h b/include/qapi/qmp/dispatch.h
> > index 5a9cf82472..0c2f467028 100644
> > --- a/include/qapi/qmp/dispatch.h
> > +++ b/include/qapi/qmp/dispatch.h
> > @@ -14,6 +14,7 @@
> > #ifndef QAPI_QMP_DISPATCH_H
> > #define QAPI_QMP_DISPATCH_H
> >
> > +#include "monitor/monitor.h"
> > #include "qemu/queue.h"
> >
> > typedef void (QmpCommandFunc)(QDict *, QObject **, Error **);
> > @@ -49,7 +50,7 @@ const char *qmp_command_name(const QmpCommand *cmd);
> > bool qmp_has_success_response(const QmpCommand *cmd);
> > QDict *qmp_error_response(Error *err);
> > QDict *qmp_dispatch(const QmpCommandList *cmds, QObject *request,
> > - bool allow_oob);
> > + bool allow_oob, Monitor *cur_mon);
> > bool qmp_is_oob(const QDict *dict);
> >
> > typedef void (*qmp_cmd_callback_fn)(const QmpCommand *cmd, void *opaque);
> > diff --git a/monitor/qmp.c b/monitor/qmp.c
> > index 8469970c69..922fdb5541 100644
> > --- a/monitor/qmp.c
> > +++ b/monitor/qmp.c
> > @@ -135,16 +135,10 @@ static void monitor_qmp_respond(MonitorQMP *mon, QDict *rsp)
> >
> > static void monitor_qmp_dispatch(MonitorQMP *mon, QObject *req)
> > {
> > - Monitor *old_mon;
> > QDict *rsp;
> > QDict *error;
> >
> > - old_mon = monitor_set_cur(&mon->common);
> > - assert(old_mon == NULL);
> > -
> > - rsp = qmp_dispatch(mon->commands, req, qmp_oob_enabled(mon));
> > -
> > - monitor_set_cur(NULL);
> > + rsp = qmp_dispatch(mon->commands, req, qmp_oob_enabled(mon), &mon->common);
>
> Long line. Happy to wrap it in my tree. A few more in PATCH 08-11.
It's 79 characters. Should be fine even with your local deviation from
the coding style to require less than that for comments?
Kevin
next prev parent reply other threads:[~2020-09-25 15:15 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 15:11 [PATCH v7 00/13] monitor: Optionally run handlers in coroutines Kevin Wolf
2020-09-09 15:11 ` [PATCH v7 01/13] monitor: Add Monitor parameter to monitor_set_cpu() Kevin Wolf
2020-09-09 15:11 ` [PATCH v7 02/13] monitor: Add Monitor parameter to monitor_get_cpu_index() Kevin Wolf
2020-09-09 15:11 ` [PATCH v7 03/13] monitor: Use getter/setter functions for cur_mon Kevin Wolf
2020-10-02 7:51 ` Markus Armbruster
2020-09-09 15:11 ` [PATCH v7 04/13] hmp: Update current monitor only in handle_hmp_command() Kevin Wolf
2020-09-09 15:11 ` [PATCH v7 05/13] qmp: Assert that no other monitor is active Kevin Wolf
2020-09-09 15:11 ` [PATCH v7 06/13] qmp: Call monitor_set_cur() only in qmp_dispatch() Kevin Wolf
2020-09-14 15:10 ` Markus Armbruster
2020-09-25 15:13 ` Kevin Wolf [this message]
2020-09-28 11:42 ` Markus Armbruster
2020-09-28 14:30 ` Kevin Wolf
2020-09-30 9:26 ` Markus Armbruster
2020-09-30 11:29 ` Kevin Wolf
2020-09-30 13:14 ` Markus Armbruster
2020-09-30 14:00 ` Kevin Wolf
2020-09-30 17:20 ` Dr. David Alan Gilbert
2020-10-01 10:14 ` Kevin Wolf
2020-10-01 16:00 ` Markus Armbruster
2020-10-02 8:04 ` Markus Armbruster
2020-09-09 15:11 ` [PATCH v7 07/13] monitor: Make current monitor a per-coroutine property Kevin Wolf
2020-09-14 15:11 ` Markus Armbruster
2020-09-25 15:23 ` Kevin Wolf
2020-09-28 7:47 ` Markus Armbruster
2020-09-28 10:42 ` Kevin Wolf
2020-09-28 12:21 ` Markus Armbruster
2020-10-02 7:53 ` Markus Armbruster
2020-09-09 15:11 ` [PATCH v7 08/13] qapi: Add a 'coroutine' flag for commands Kevin Wolf
2020-09-14 15:15 ` Markus Armbruster
2020-09-25 15:37 ` Kevin Wolf
2020-09-28 8:23 ` Markus Armbruster
2020-10-02 7:53 ` Markus Armbruster
2020-10-02 7:59 ` Markus Armbruster
2020-09-09 15:11 ` [PATCH v7 09/13] qmp: Move dispatcher to a coroutine Kevin Wolf
2020-09-14 15:30 ` Markus Armbruster
2020-09-25 15:38 ` Kevin Wolf
2020-09-28 8:24 ` Markus Armbruster
2020-10-02 8:01 ` Markus Armbruster
2020-09-09 15:11 ` [PATCH v7 10/13] hmp: Add support for coroutine command handlers Kevin Wolf
2020-09-16 9:46 ` Dr. David Alan Gilbert
2020-10-02 8:01 ` Markus Armbruster
2020-09-09 15:11 ` [PATCH v7 11/13] util/async: Add aio_co_reschedule_self() Kevin Wolf
2020-09-15 14:25 ` Stefan Hajnoczi
2020-10-02 8:01 ` Markus Armbruster
2020-09-09 15:11 ` [PATCH v7 12/13] block: Add bdrv_co_move_to_aio_context() Kevin Wolf
2020-09-15 14:31 ` Stefan Hajnoczi
2020-09-25 16:00 ` Kevin Wolf
2020-09-28 8:59 ` Stefan Hajnoczi
2020-09-28 10:21 ` Kevin Wolf
2020-09-09 15:11 ` [PATCH v7 13/13] block: Convert 'block_resize' to coroutine Kevin Wolf
2020-09-15 14:57 ` Stefan Hajnoczi
2020-09-25 16:07 ` Kevin Wolf
2020-09-28 9:05 ` Stefan Hajnoczi
2020-09-28 10:33 ` Kevin Wolf
2020-09-09 15:24 ` [PATCH v7 00/13] monitor: Optionally run handlers in coroutines no-reply
2020-09-10 13:24 ` Stefan Hajnoczi
2020-09-14 15:09 ` Markus Armbruster
2020-09-15 14:58 ` Stefan Hajnoczi
2020-09-25 17:15 ` Kevin Wolf
2020-09-28 8:46 ` Stefan Hajnoczi
2020-09-28 9:47 ` Kevin Wolf
2020-09-28 9:30 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200925151304.GE5731@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).