qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>, "Kevin Wolf" <kwolf@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	qemu-block@nongnu.org, "David Hildenbrand" <david@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Michael Roth" <mdroth@linux.vnet.ibm.com>,
	"Amit Shah" <amit@kernel.org>, "Max Reitz" <mreitz@redhat.com>,
	"Eric Auger" <eric.auger@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [RFC v3 3/6] qmp: decode feature bits in virtio-status
Date: Fri, 8 May 2020 10:54:30 +0800	[thread overview]
Message-ID: <1b4c1915-b5d5-bc2d-9b02-b9483eebbe80@redhat.com> (raw)
In-Reply-To: <20200507114927.6733-4-lvivier@redhat.com>


On 2020/5/7 下午7:49, Laurent Vivier wrote:
> Display feature names instead of a features bitmap for host, guest
> and backend.
>
> Decode features according device type, transport features are
> on the first line. Undecoded bits (if any) are stored in a separate
> field.
>
> Signed-off-by: Laurent Vivier<lvivier@redhat.com>


This is really useful. I wonder maybe we need something similar in 
driver side, current sysfs can only display magic binary numbers.

Thanks



  parent reply	other threads:[~2020-05-08  2:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200507114927.6733-1-lvivier@redhat.com>
     [not found] ` <20200507114927.6733-2-lvivier@redhat.com>
2020-05-07 15:38   ` [RFC v3 1/6] qmp: add QMP command x-debug-query-virtio Eric Blake
     [not found] ` <20200507114927.6733-7-lvivier@redhat.com>
2020-05-07 15:51   ` [RFC v3 6/6] hmp: add x-debug-virtio commands Eric Blake
     [not found] ` <20200507114927.6733-4-lvivier@redhat.com>
2020-05-07 15:47   ` [RFC v3 3/6] qmp: decode feature bits in virtio-status Eric Blake
2020-05-08  2:54   ` Jason Wang [this message]
     [not found] ` <20200507114927.6733-5-lvivier@redhat.com>
2020-05-08  2:57   ` [RFC v3 4/6] qmp: add QMP command x-debug-virtio-queue-status Jason Wang
2020-05-15 15:16     ` Laurent Vivier
2020-05-18  3:31       ` Jason Wang
     [not found] ` <20200507114927.6733-6-lvivier@redhat.com>
2020-05-08  3:03   ` [RFC v3 5/6] qmp: add QMP command x-debug-virtio-queue-element Jason Wang

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=1b4c1915-b5d5-bc2d-9b02-b9483eebbe80@redhat.com \
    --to=jasowang@redhat.com \
    --cc=amit@kernel.org \
    --cc=armbru@redhat.com \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=fam@euphon.net \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --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).