qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 v3 0/1] util/async-teardown: wire up query-command-line-options
Date: Fri, 24 Mar 2023 18:45:58 +0100	[thread overview]
Message-ID: <20230324174559.44933-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.

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            | 14 ++++++++++++++
 qemu-options.hx       | 35 ++++++++++++++++++++++++-----------
 util/async-teardown.c | 21 +++++++++++++++++++++
 3 files changed, 59 insertions(+), 11 deletions(-)

-- 
2.39.2



             reply	other threads:[~2023-03-24 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 17:45 Claudio Imbrenda [this message]
2023-03-24 17:45 ` [PATCH v3 1/1] util/async-teardown: wire up query-command-line-options Claudio Imbrenda
2023-03-24 17:56   ` Thomas Huth
2023-03-24 19:10     ` Claudio Imbrenda
2023-03-27  7:06       ` Thomas Huth
2023-03-27  7:20   ` Thomas Huth

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=20230324174559.44933-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).