All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: berrange@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] qemu-option: do not suggest using the delay option
Date: Thu, 04 Mar 2021 17:37:39 +0100	[thread overview]
Message-ID: <87eegudgdo.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20210304111743.118752-1-pbonzini@redhat.com> (Paolo Bonzini's message of "Thu, 4 Mar 2021 12:17:43 +0100")

Paolo Bonzini <pbonzini@redhat.com> writes:

> The "delay" option was a hack that was introduced to allow writing "nodelay".
> We are adding a "nodelay" option to be used as "nodelay=on", so recommend it
> instead of "delay".
>
> This is quite ugly, but a proper deprecation of "delay"
> cannot be done if QEMU starts suggesting it.  Since it's the
> only case I opted for this very much ad-hoc patch.
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  docs/system/deprecated.rst | 6 ++++++
>  util/qemu-option.c         | 6 +++++-
>  2 files changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst
> index fcf0ca4068..cfabe69846 100644
> --- a/docs/system/deprecated.rst
> +++ b/docs/system/deprecated.rst
> @@ -134,6 +134,12 @@ Boolean options such as ``share=on``/``share=off`` could be written
>  in short form as ``share`` and ``noshare``.  This is now deprecated
>  and will cause a warning.
>  
> +``delay`` option for socket character devices (since 6.0)
> +'''''''''''''''''''''''''''''''''''''''''''''''''''''''''
> +
> +The replacement for the ``nodelay`` short-form boolean option is ``nodelay=on``
> +rather than ``delay=off``.
> +
>  ``--enable-fips`` (since 6.0)
>  '''''''''''''''''''''''''''''
>  
> diff --git a/util/qemu-option.c b/util/qemu-option.c
> index 40564a12eb..9678d5b682 100644
> --- a/util/qemu-option.c
> +++ b/util/qemu-option.c
> @@ -785,7 +785,11 @@ static const char *get_opt_name_value(const char *params,
>              }
>              if (!is_help && warn_on_flag) {
>                  warn_report("short-form boolean option '%s%s' deprecated", prefix, *name);
> -                error_printf("Please use %s=%s instead\n", *name, *value);
> +                if (g_str_equal(*name, "delay")) {
> +                    error_printf("Please use nodelay=%s instead\n", prefix[0] ? "on" : "off");
> +                } else {
> +                    error_printf("Please use %s=%s instead\n", *name, *value);
> +                }
>              }
>          }
>      } else {

I agree it's ugly, but I don't have better ideas, and it'll go away
eventually.

The warning gets emitted for any QemuOpts parameter named "delay" used
without a value, not just socket chardev's parameter.  Could result in
somewhat misleading warnings, but trying to avoid them seems a waste of
our time.

Should we mention this in the commit message?  Or even in a code
comment?  Up do you.

Reviewed-by: Markus Armbruster <armbru@redhat.com>



      parent reply	other threads:[~2021-03-04 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 11:17 [PATCH v2] qemu-option: do not suggest using the delay option Paolo Bonzini
2021-03-04 11:21 ` no-reply
2021-03-04 16:37 ` Markus Armbruster [this message]

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=87eegudgdo.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.