From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL v2 20/32] monitor: Peel off @mon_global wrapper
Date: Tue, 3 Jul 2018 23:35:44 +0200 [thread overview]
Message-ID: <20180703213556.20619-21-armbru@redhat.com> (raw)
In-Reply-To: <20180703213556.20619-1-armbru@redhat.com>
Wrapping global variables in a struct without a use for the wrapper
struct buys us nothing but longer lines. Unwrap them.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-Id: <20180703085358.13941-21-armbru@redhat.com>
---
monitor.c | 60 +++++++++++++++++++++++++++----------------------------
1 file changed, 29 insertions(+), 31 deletions(-)
diff --git a/monitor.c b/monitor.c
index b3c5dcc685..26de90e4d2 100644
--- a/monitor.c
+++ b/monitor.c
@@ -211,7 +211,7 @@ struct Monitor {
/*
* State used only in the thread "owning" the monitor.
- * If @use_io_thread, this is mon_global.mon_iothread.
+ * If @use_io_thread, this is @mon_iothread.
* Else, it's the main thread.
* These members can be safely accessed without locks.
*/
@@ -240,14 +240,13 @@ struct Monitor {
int mux_out;
};
-/* Let's add monitor global variables to this struct. */
-static struct {
- IOThread *mon_iothread;
- /* Bottom half to dispatch the requests received from I/O thread */
- QEMUBH *qmp_dispatcher_bh;
- /* Bottom half to deliver the responses back to clients */
- QEMUBH *qmp_respond_bh;
-} mon_global;
+IOThread *mon_iothread;
+
+/* Bottom half to dispatch the requests received from I/O thread */
+QEMUBH *qmp_dispatcher_bh;
+
+/* Bottom half to deliver the responses back to clients */
+QEMUBH *qmp_respond_bh;
struct QMPRequest {
/* Owner of the request */
@@ -531,7 +530,7 @@ static void monitor_json_emitter(Monitor *mon, QObject *data)
qemu_mutex_lock(&mon->qmp.qmp_queue_lock);
g_queue_push_tail(mon->qmp.qmp_responses, qobject_ref(data));
qemu_mutex_unlock(&mon->qmp.qmp_queue_lock);
- qemu_bh_schedule(mon_global.qmp_respond_bh);
+ qemu_bh_schedule(qmp_respond_bh);
} else {
/*
* If not using monitor I/O thread, then we are in main thread.
@@ -4219,7 +4218,7 @@ static void monitor_qmp_bh_dispatcher(void *data)
qmp_request_free(req_obj);
/* Reschedule instead of looping so the main loop stays responsive */
- qemu_bh_schedule(mon_global.qmp_dispatcher_bh);
+ qemu_bh_schedule(qmp_dispatcher_bh);
}
#define QMP_REQ_QUEUE_LEN_MAX (8)
@@ -4305,7 +4304,7 @@ static void handle_qmp_command(JSONMessageParser *parser, GQueue *tokens)
qemu_mutex_unlock(&mon->qmp.qmp_queue_lock);
/* Kick the dispatcher routine */
- qemu_bh_schedule(mon_global.qmp_dispatcher_bh);
+ qemu_bh_schedule(qmp_dispatcher_bh);
}
static void monitor_qmp_read(void *opaque, const uint8_t *buf, int size)
@@ -4358,7 +4357,7 @@ int monitor_suspend(Monitor *mon)
* Kick I/O thread to make sure this takes effect. It'll be
* evaluated again in prepare() of the watch object.
*/
- aio_notify(iothread_get_aio_context(mon_global.mon_iothread));
+ aio_notify(iothread_get_aio_context(mon_iothread));
}
trace_monitor_suspend(mon, 1);
@@ -4378,7 +4377,7 @@ void monitor_resume(Monitor *mon)
* kick the thread in case it's sleeping.
*/
if (mon->use_io_thread) {
- aio_notify(iothread_get_aio_context(mon_global.mon_iothread));
+ aio_notify(iothread_get_aio_context(mon_iothread));
}
} else {
assert(mon->rs);
@@ -4516,36 +4515,35 @@ static void sortcmdlist(void)
static GMainContext *monitor_get_io_context(void)
{
- return iothread_get_g_main_context(mon_global.mon_iothread);
+ return iothread_get_g_main_context(mon_iothread);
}
static AioContext *monitor_get_aio_context(void)
{
- return iothread_get_aio_context(mon_global.mon_iothread);
+ return iothread_get_aio_context(mon_iothread);
}
static void monitor_iothread_init(void)
{
- mon_global.mon_iothread = iothread_create("mon_iothread",
- &error_abort);
+ mon_iothread = iothread_create("mon_iothread", &error_abort);
/*
* This MUST be on main loop thread since we have commands that
* have assumption to be run on main loop thread. It would be
* nice that one day we can remove this assumption in the future.
*/
- mon_global.qmp_dispatcher_bh = aio_bh_new(iohandler_get_aio_context(),
- monitor_qmp_bh_dispatcher,
- NULL);
+ qmp_dispatcher_bh = aio_bh_new(iohandler_get_aio_context(),
+ monitor_qmp_bh_dispatcher,
+ NULL);
/*
* Unlike the dispatcher BH, this must be run on the monitor I/O
* thread, so that monitors that are using I/O thread will make
* sure read/write operations are all done on the I/O thread.
*/
- mon_global.qmp_respond_bh = aio_bh_new(monitor_get_aio_context(),
- monitor_qmp_bh_responder,
- NULL);
+ qmp_respond_bh = aio_bh_new(monitor_get_aio_context(),
+ monitor_qmp_bh_responder,
+ NULL);
}
void monitor_init_globals(void)
@@ -4702,7 +4700,7 @@ void monitor_cleanup(void)
* we need to unregister from chardev below in
* monitor_data_destroy(), and chardev is not thread-safe yet
*/
- iothread_stop(mon_global.mon_iothread);
+ iothread_stop(mon_iothread);
/*
* After we have I/O thread to send responses, it's possible that
@@ -4723,13 +4721,13 @@ void monitor_cleanup(void)
qemu_mutex_unlock(&monitor_lock);
/* QEMUBHs needs to be deleted before destroying the I/O thread */
- qemu_bh_delete(mon_global.qmp_dispatcher_bh);
- mon_global.qmp_dispatcher_bh = NULL;
- qemu_bh_delete(mon_global.qmp_respond_bh);
- mon_global.qmp_respond_bh = NULL;
+ qemu_bh_delete(qmp_dispatcher_bh);
+ qmp_dispatcher_bh = NULL;
+ qemu_bh_delete(qmp_respond_bh);
+ qmp_respond_bh = NULL;
- iothread_destroy(mon_global.mon_iothread);
- mon_global.mon_iothread = NULL;
+ iothread_destroy(mon_iothread);
+ mon_iothread = NULL;
}
QemuOptsList qemu_mon_opts = {
--
2.17.1
next prev parent reply other threads:[~2018-07-03 21:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 21:35 [Qemu-devel] [PULL v2 00/32] Monitor patches for 2018-07-03 Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 01/32] qmp: Say "out-of-band" instead of "Out-Of-Band" Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 02/32] monitor: Spell "I/O thread" consistently in comments Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 03/32] docs/interop/qmp: Improve OOB documentation Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 04/32] qmp: Document COMMAND_DROPPED design flaw Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 05/32] qmp: Get rid of x-oob-test command Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 06/32] tests/qmp-test: Test in-band command doesn't overtake Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 07/32] qmp: Make "id" optional again even in "oob" monitors Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 08/32] tests/test-qga: Demonstrate the guest-agent ignores "id" Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 09/32] qmp qemu-ga: Revert change that accidentally made qemu-ga accept "id" Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 10/32] tests/test-qga: Demonstrate the guest-agent ignores "control" Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 11/32] qmp qemu-ga: Fix qemu-ga not to accept "control" Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 12/32] qmp: Redo how the client requests out-of-band execution Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 13/32] qmp: Revert change to handle_qmp_command tracepoint Markus Armbruster
2018-07-19 11:07 ` Peter Maydell
2018-07-19 12:22 ` Markus Armbruster
2018-07-19 12:25 ` Peter Maydell
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 14/32] qmp: Always free QMPRequest with qmp_request_free() Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 15/32] qmp: Simplify code around monitor_qmp_dispatch_one() Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 16/32] tests/qmp-test: Demonstrate QMP errors jumping the queue Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 17/32] qmp: Don't let malformed in-band commands jump " Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 18/32] qmp: Don't let JSON errors " Markus Armbruster
2018-07-10 13:20 ` Kevin Wolf
2018-07-10 14:02 ` Marc-André Lureau
2018-07-11 8:36 ` Kevin Wolf
2018-07-11 14:13 ` Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 19/32] monitor: Rename use_io_thr to use_io_thread Markus Armbruster
2018-07-03 21:35 ` Markus Armbruster [this message]
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 21/32] qobject: New qdict_from_jsonf_nofail() Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 22/32] qmp: De-duplicate error response building Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 23/32] qmp: Use QDict * instead of QObject * for response objects Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 24/32] qmp: Replace monitor_json_emitter{, raw}() by qmp_{queue, send}_response() Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 25/32] qmp: Replace get_qmp_greeting() by qmp_greeting() Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 26/32] qmp: Simplify monitor_qmp_respond() Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 27/32] qmp: Add some comments around null responses Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 28/32] qmp: Switch timestamp_put() to qdict_from_jsonf_nofail() Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 29/32] qobject: Let qobject_from_jsonf() fail instead of abort Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 30/32] qmp: Clean up capability negotiation after commit 02130314d8c Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 31/32] monitor: Improve some comments Markus Armbruster
2018-07-03 21:35 ` [Qemu-devel] [PULL v2 32/32] qapi: Polish command flags documentation in qapi-code-gen.txt Markus Armbruster
2018-07-05 12:33 ` [Qemu-devel] [PULL v2 00/32] Monitor patches for 2018-07-03 Peter Maydell
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=20180703213556.20619-21-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).