From: "Michael S. Tsirkin" <mst@redhat.com>
To: Hyman Huang <yong.huang@smartx.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH v3 0/3] Adjust the output of x-query-virtio-status
Date: Tue, 13 Feb 2024 05:25:33 -0500 [thread overview]
Message-ID: <20240213052503-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <cover.1706883915.git.yong.huang@smartx.com>
On Fri, Feb 02, 2024 at 10:32:14PM +0800, Hyman Huang wrote:
> Sorry for the late post of version 3. The modifications are as follows:
>
> v3:
> - Rebase on master
> - Use the refined commit message furnished by Markus for [PATCH v2 1/2]
> - Drop the [PATCH v2 2/2]
> - Add [PATCH v3 2/3] to declare the decoding functions to static
> - Add [PATCH v3 3/3] to Define VhostDeviceProtocols and
> VirtioDeviceFeatures as plain C types
>
> Since Markus inspired all of the alterations above, we would like to
> thank him for his contribution to this series.
>
> Please review,
> Yong
Markus do you think you can take a look at this?
> v2:
> - Changing the hmp_virtio_dump_xxx function signatures to implement
> the bitmap decoding, suggested by Philippe.
>
> This patchset is derived from the series:
> https://lore.kernel.org/qemu-devel/cover.1699793550.git.yong.huang@smartx.com/
> Please go to the link to see more background information.
>
> The following points are what we have done in the patchset:
> 1. Take the policy of adding human-readable output just in HMP.
> 2. For the HMP output, display the human-readable information and
> drop the unknown bits in practice.
> 3. For the QMP output, remove the descriptive strings and only
> display bits encoded as numbers.
>
> Hyman Huang (3):
> qmp: Switch x-query-virtio-status back to numeric encoding
> virtio: Declare the decoding functions to static
> qapi: Define VhostDeviceProtocols and VirtioDeviceFeatures as plain C
> types
>
> hw/virtio/meson.build | 3 +-
> hw/virtio/virtio-hmp-cmds.c | 702 +++++++++++++++++++++++++++++++++++-
> hw/virtio/virtio-qmp.c | 684 +----------------------------------
> hw/virtio/virtio-qmp.h | 3 -
> qapi/virtio.json | 231 +-----------
> 5 files changed, 723 insertions(+), 900 deletions(-)
>
> --
> 2.31.1
next prev parent reply other threads:[~2024-02-13 10:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 14:32 [PATCH v3 0/3] Adjust the output of x-query-virtio-status Hyman Huang
2024-02-02 14:32 ` [PATCH v3 1/3] qmp: Switch x-query-virtio-status back to numeric encoding Hyman Huang
2024-02-13 10:26 ` Michael S. Tsirkin
2024-02-15 12:49 ` Yong Huang
2024-02-19 15:32 ` Markus Armbruster
2024-02-20 1:27 ` Yong Huang
2024-02-19 15:18 ` Markus Armbruster
2024-02-02 14:32 ` [PATCH v3 2/3] virtio: Declare the decoding functions to static Hyman Huang
2024-02-19 15:38 ` Markus Armbruster
2024-02-21 3:59 ` Yong Huang
2024-02-02 14:32 ` [PATCH v3 3/3] qapi: Define VhostDeviceProtocols and VirtioDeviceFeatures as plain C types Hyman Huang
2024-02-19 15:33 ` Markus Armbruster
2024-02-13 10:25 ` Michael S. Tsirkin [this message]
2024-02-13 13:30 ` [PATCH v3 0/3] Adjust the output of x-query-virtio-status 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=20240213052503-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yong.huang@smartx.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).