qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: huangy81@chinatelecom.cn, qemu-devel <qemu-devel@nongnu.org>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>,  Eric Blake <eblake@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Stefano Garzarella <sgarzare@redhat.com>,
	Raphael Norwitz <raphael.norwitz@nutanix.com>
Subject: Re: [PATCH RFC 2/4] hmp: Add "info netdev" cmd
Date: Wed, 2 Nov 2022 08:13:30 +0100	[thread overview]
Message-ID: <da79f2db-c430-bf6a-79a4-c005935d4a5f@redhat.com> (raw)
In-Reply-To: <4e96b2beac69aa865777eb95330b9852a36353c7.1667232396.git.huangy81@chinatelecom.cn>

On 31/10/2022 17.19, huangy81@chinatelecom.cn wrote:
> From: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>
> 
> Introduce "info netdev" command so developers can play with
> it easier.
> 
> Signed-off-by: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>
> ---
>   hmp-commands-info.hx  | 14 ++++++++++++++
>   include/monitor/hmp.h |  1 +
>   net/net.c             | 31 +++++++++++++++++++++++++++++++
>   3 files changed, 46 insertions(+)
> 
> diff --git a/hmp-commands-info.hx b/hmp-commands-info.hx
> index 754b1e8..217843c 100644
> --- a/hmp-commands-info.hx
> +++ b/hmp-commands-info.hx
> @@ -880,6 +880,20 @@ SRST
>       Display the vcpu dirty page limit information.
>   ERST
>   
> +    {
> +        .name       = "netdev",
> +        .args_type  = "",
> +        .params     = "",
> +        .help       = "show information about netdev, guest acked features are "
> +                      "also printed if supporting virtio-net dataplane offloading",
> +        .cmd        = hmp_info_netdev,
> +    },
> +
> +SRST
> +  ``info netdev``
> +    Display information about netdev.
> +ERST

Hmm, so according to the information, this shows information about the 
virtio *frontend*, but netdev is about *backends* (like TAP, slirp, VDE, 
...) ... so this is definitely also the wrong naming here. Maybe rather 
"info virtio-net" or "info vhost-net" or something like that?

  Thomas



  reply	other threads:[~2022-11-02  7:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 16:18 [PATCH RFC 0/4] Export netdev capabilities and information huangy81
2022-10-31 16:18 ` [PATCH RFC 1/4] net: Introduce qmp cmd "query-netdev" huangy81
2022-11-02  5:42   ` Jason Wang
2022-11-02  6:41     ` Michael S. Tsirkin
2022-11-02 15:36       ` Hyman
2022-11-02  7:10     ` Thomas Huth
2022-11-02 15:37       ` Hyman
2022-11-02 15:31     ` Hyman
2022-10-31 16:19 ` [PATCH RFC 2/4] hmp: Add "info netdev" cmd huangy81
2022-11-02  7:13   ` Thomas Huth [this message]
2022-10-31 16:19 ` [PATCH RFC 3/4] hmp: Add netdev information into output of hmp cmd "info network" huangy81
2022-10-31 16:19 ` [PATCH RFC 4/4] vhost-user-test: Add negotiated features check huangy81

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=da79f2db-c430-bf6a-79a4-c005935d4a5f@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=huangy81@chinatelecom.cn \
    --cc=jasowang@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=raphael.norwitz@nutanix.com \
    --cc=sgarzare@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).