From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, david@redhat.com, thuth@redhat.com,
borntraeger@de.ibm.com, frankja@linux.ibm.com,
fiuczy@linux.ibm.com, pasic@linux.ibm.com, nsg@linux.ibm.com,
berrange@redhat.com, alex.bennee@linaro.org, armbru@redhat.com
Subject: [PATCH v4 0/1] util/async-teardown: wire up query-command-line-options
Date: Mon, 27 Mar 2023 14:03:56 +0200 [thread overview]
Message-ID: <20230327120357.34743-1-imbrenda@linux.ibm.com> (raw)
The recently introduced -async-teardown commandline option was not
wired up properly and did not show up in the output of the QMP command
query-command-line-options. This means that libvirt will have no way to
discover whether the feature is supported.
This patch fixes the issue by adding a new -teardown commandline option
with an async=on|off parameter, correctly wired up so that it appears
in the output of query-command-line-options.
v3->v4
* completely remove the useless -async-teardown option, since it was
not wired up properly and it had no users [thomas]
* QEMU should be always uppercase in text and documentation [thomas]
* if the new -teardown option fails to parse, exit immediately instead
of returning an error [thomas]
v2->v3
* add a new teardown option with an async parameter [Markus]
* reworded documentation of existing -async-teardown option so that it
points to the new teardown option
v1->v2
* remove the unneeded .implied_opt_name initializer [Thomas]
Claudio Imbrenda (1):
util/async-teardown: wire up query-command-line-options
os-posix.c | 15 +++++++++++++--
qemu-options.hx | 33 +++++++++++++++++++--------------
util/async-teardown.c | 21 +++++++++++++++++++++
3 files changed, 53 insertions(+), 16 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-27 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 12:03 Claudio Imbrenda [this message]
2023-03-27 12:03 ` [PATCH v4 1/1] util/async-teardown: wire up query-command-line-options Claudio Imbrenda
2023-03-27 12:59 ` 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=20230327120357.34743-1-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=fiuczy@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).