From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: damien.hedde@greensocs.com, berrange@redhat.com,
mark.burton@greensocs.com, armbru@redhat.com, f4bug@amsat.org,
mirela.grujic@greensocs.com
Subject: [RFC PATCH 0/3] introduce QMP-only binaries
Date: Tue, 8 Feb 2022 09:44:55 -0500 [thread overview]
Message-ID: <20220208144458.1079634-1-pbonzini@redhat.com> (raw)
These three patches introduce a new system emulation binary qemu-qmp-*
that does nothing but start a QMP monitor (via systemd activation
protocol if possible, otherwise on stdio). The idea is that the
creation of the machine would happen through new commands such as
machine-set, accel-set, etc.
Patches 1 and 2 simply avoid that {'execute':'quit'} crashes; that's
more or less the extent of my testing.
Paolo
Paolo Bonzini (3):
migration: allow calling migration_shutdown without a prior
initialization
net: initialize global variables early
introduce qemu-qmp-*
hw/net/xen_nic.c | 20 +++---
include/net/net.h | 1 +
meson.build | 16 +++--
migration/migration.c | 4 ++
net/net.c | 5 +-
softmmu/{vl.c => climain.c} | 2 +-
softmmu/meson.build | 1 -
softmmu/qmpmain.c | 120 ++++++++++++++++++++++++++++++++++++
softmmu/runstate.c | 1 +
9 files changed, 153 insertions(+), 17 deletions(-)
rename softmmu/{vl.c => climain.c} (99%)
create mode 100644 softmmu/qmpmain.c
--
2.31.1
next reply other threads:[~2022-02-08 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 14:44 Paolo Bonzini [this message]
2022-02-08 14:44 ` [RFC PATCH 1/3] migration: allow calling migration_shutdown without a prior initialization Paolo Bonzini
2022-02-08 14:44 ` [RFC PATCH 2/3] net: initialize global variables early Paolo Bonzini
2022-02-08 14:47 ` Philippe Mathieu-Daudé via
2022-02-08 14:44 ` [RFC PATCH 3/3] introduce qemu-qmp-* Paolo Bonzini
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=20220208144458.1079634-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=damien.hedde@greensocs.com \
--cc=f4bug@amsat.org \
--cc=mark.burton@greensocs.com \
--cc=mirela.grujic@greensocs.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).