qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>
Subject: [Qemu-devel] [PULL 6/7] monitor: move init global earlier
Date: Mon, 18 Jun 2018 16:08:53 +0200	[thread overview]
Message-ID: <20180618140854.17824-7-armbru@redhat.com> (raw)
In-Reply-To: <20180618140854.17824-1-armbru@redhat.com>

From: Peter Xu <peterx@redhat.com>

Before this patch, monitor fd helpers might be called even earlier than
monitor_init_globals().  This can be problematic.

After previous work, now monitor_init_globals() does not depend on
accelerator initialization any more.  Call it earlier (before CLI
parsing; that's where the monitor APIs might be called) to make sure it
is called before any of the monitor APIs.

Suggested-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20180608035511.7439-7-peterx@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
---
 vl.c | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/vl.c b/vl.c
index 6e34fb348d..b3426e03d0 100644
--- a/vl.c
+++ b/vl.c
@@ -2978,6 +2978,7 @@ int main(int argc, char **argv, char **envp)
 
     runstate_init();
     postcopy_infrastructure_init();
+    monitor_init_globals();
 
     if (qcrypto_init(&err) < 0) {
         error_reportf_err(err, "cannot initialize crypto: ");
@@ -4412,12 +4413,6 @@ int main(int argc, char **argv, char **envp)
     default_drive(default_floppy, snapshot, IF_FLOPPY, 0, FD_OPTS);
     default_drive(default_sdcard, snapshot, IF_SD, 0, SD_OPTS);
 
-    /*
-     * Note: qtest_enabled() (which is used in monitor_qapi_event_init())
-     * depends on configure_accelerator() above.
-     */
-    monitor_init_globals();
-
     if (qemu_opts_foreach(qemu_find_opts("mon"),
                           mon_init_func, NULL, NULL)) {
         exit(1);
-- 
2.17.1

  parent reply	other threads:[~2018-06-18 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 14:08 [Qemu-devel] [PULL 0/7] monitor: Thread safety improvements Markus Armbruster
2018-06-18 14:08 ` [Qemu-devel] [PULL 1/7] monitor: rename out_lock to mon_lock Markus Armbruster
2018-06-18 14:08 ` [Qemu-devel] [PULL 2/7] monitor: protect mon->fds with mon_lock Markus Armbruster
2018-06-18 14:08 ` [Qemu-devel] [PULL 3/7] monitor: more comments on lock-free elements Markus Armbruster
2018-06-18 14:08 ` [Qemu-devel] [PULL 4/7] monitor: fix comment for monitor_lock Markus Armbruster
2018-06-18 14:08 ` [Qemu-devel] [PULL 5/7] monitor: remove event_clock_type Markus Armbruster
2018-06-18 14:08 ` Markus Armbruster [this message]
2018-09-05 15:05   ` [Qemu-devel] [PULL 6/7] monitor: move init global earlier Wolfgang Bumiller
2018-09-06  3:38     ` Peter Xu
2018-06-18 14:08 ` [Qemu-devel] [PULL 7/7] monitor: add lock to protect mon_fdsets Markus Armbruster
2018-06-19 15:04 ` [Qemu-devel] [PULL 0/7] monitor: Thread safety improvements 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=20180618140854.17824-7-armbru@redhat.com \
    --to=armbru@redhat.com \
    --cc=peterx@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).