From: Thomas Huth <thuth@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: libvir-list@redhat.com, Claudio Imbrenda <imbrenda@linux.ibm.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH] os-posix: Allow 'chroot' via '-run-with' and deprecate the old '-chroot' option
Date: Fri, 30 Jun 2023 18:11:54 +0200 [thread overview]
Message-ID: <a4706aa4-5cf7-0fa1-7010-1eb7d64f169c@redhat.com> (raw)
In-Reply-To: <258917a6-62a3-8d5d-c651-4a11942801c4@tls.msk.ru>
On 30/06/2023 17.56, Michael Tokarev wrote:
> 30.06.2023 18:01, Thomas Huth wrote:
>> We recently introduced "-run-with" for options that influence the
>> runtime behavior of QEMU. This option has the big advantage that it
>> can group related options (so that it is easier for the users to spot
>> them) and that the options become introspectable via QMP this way.
>> So let's start moving more switches into this option group, starting
>> with "-chroot" now.
> ...
>> +static QemuOptsList qemu_run_with_opts = {
>> + .name = "run-with",
>> + .head = QTAILQ_HEAD_INITIALIZER(qemu_run_with_opts.head),
>> + .desc = {
>> +#if defined(CONFIG_LINUX)
>> + {
>> + .name = "async-teardown",
>> + .type = QEMU_OPT_BOOL,
>> + },
>> +#endif
>> + {
>> + .name = "chroot",
>> + .type = QEMU_OPT_STRING,
>> + },
>> + { /* end of list */ }
>> + },
>> +};
>> +
>> +static void register_teardown(void)
>> +{
>> + qemu_add_opts(&qemu_run_with_opts);
>> +}
>> +opts_init(register_teardown);
>
> Hmm.. Is it still register_teardown? :)
Drat. Should be something like "register_runwith" now, of course. Thanks for
spotting it!
Thomas
> Other than that,
>
> Reviewed-by: Michael Tokarev <mjt@tls.msk.ru>
>
> /mjt
>
next prev parent reply other threads:[~2023-06-30 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 15:01 [PATCH] os-posix: Allow 'chroot' via '-run-with' and deprecate the old '-chroot' option Thomas Huth
2023-06-30 15:18 ` Claudio Imbrenda
2023-06-30 15:56 ` Michael Tokarev
2023-06-30 16:11 ` Thomas Huth [this message]
2023-06-30 19:14 ` Ján Tomko
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=a4706aa4-5cf7-0fa1-7010-1eb7d64f169c@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=libvir-list@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@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).