All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH] hmp/info_migration: formatting migration capability output
Date: Fri, 02 Aug 2019 07:24:34 +0200	[thread overview]
Message-ID: <87a7csm965.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190802020716.11985-1-richardw.yang@linux.intel.com> (Wei Yang's message of "Fri, 2 Aug 2019 10:07:16 +0800")

Subject doesn't quite conform to conventions.  Suggest

    hmp: Improve how "info migrate" formats capabilities

Wei Yang <richardw.yang@linux.intel.com> writes:

> Current we put all migration capability in one line, which make it hard
> to read them and someone them are missed due to terminal width.
>
> This patch formats it to print 4 in one line, which looks like this now:
>
> capabilities:
>               xbzrle: off         rdma-pin-all: off        auto-converge: off          zero-blocks: off
>             compress:  on               events: off         postcopy-ram: off               x-colo: off
>          release-ram: off                block: off          return-path: off pause-before-switchover: off
>              multifd: off        dirty-bitmaps: off   postcopy-blocktime: off  late-block-activate: off
>      x-ignore-shared: off
>
> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
> ---
>  monitor/hmp-cmds.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/monitor/hmp-cmds.c b/monitor/hmp-cmds.c
> index 5ca3ebe942..29ce5b73e4 100644
> --- a/monitor/hmp-cmds.c
> +++ b/monitor/hmp-cmds.c
> @@ -229,9 +229,13 @@ void hmp_info_migrate(Monitor *mon, const QDict *qdict)
>  
>      /* do not display parameters during setup */
>      if (info->has_status && caps) {
> +        int index = 0;
>          monitor_printf(mon, "capabilities: ");
> -        for (cap = caps; cap; cap = cap->next) {
> -            monitor_printf(mon, "%s: %s ",
> +        for (cap = caps; cap; cap = cap->next, index++) {
> +            if (!(index % 4)) {
> +                monitor_printf(mon, "\n");
> +            }
> +            monitor_printf(mon, "%20s: %3s ",
>                             MigrationCapability_str(cap->value->capability),
>                             cap->value->state ? "on" : "off");
>          }

This assumes migration capability names are at most 20 characters long.
late-block-activate is pushing it already: 19 characters.

It adds up to 104 characters per line, which is rather wide.

What about putting each capability on its own line, just like globals,
and just like "info migrate_capabilities"?

(qemu) info migrate
globals:
store-global-state: on
only-migratable: off
send-configuration: on
send-section-footer: on
decompress-error-check: on
clear-bitmap-shift: 18
capabilities:
xbzrle: off
rdma-pin-all: off
auto-converge: off
[...]


  reply	other threads:[~2019-08-02  5:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02  2:07 [Qemu-devel] [PATCH] hmp/info_migration: formatting migration capability output Wei Yang
2019-08-02  5:24 ` Markus Armbruster [this message]
2019-08-02  5:43   ` Wei Yang
2019-08-02 10:02     ` Dr. David Alan Gilbert
2019-08-02 21:33       ` Wei Yang
2019-08-02 12:12     ` 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=87a7csm965.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richardw.yang@linux.intel.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 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.