qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: markmc@redhat.com, rusty@rustcorp.com.au, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-net: Remove RX_EXTRA feature
Date: Sun, 14 Jun 2009 12:39:54 +0300	[thread overview]
Message-ID: <20090614093954.GB6959@redhat.com> (raw)
In-Reply-To: <20090612191626.4227.7273.stgit@kvm.aw>

On Fri, Jun 12, 2009 at 01:17:04PM -0600, Alex Williamson wrote:
> No need to use a feature bit to identify the RX modes.  The guest
> will get an error back if the backend doesn't support these controls.
> 
> Signed-off-by: Alex Williamson <alex.williamson@hp.com>

What's the motivation here - are we running out of feature bits already?
Using feature bits for everything makes the interface more consistent
and IMO easier to use.


> ---
> 
>  hw/virtio-net.c |    3 +--
>  hw/virtio-net.h |    8 ++++----
>  2 files changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/hw/virtio-net.c b/hw/virtio-net.c
> index d584287..fd5753a 100644
> --- a/hw/virtio-net.c
> +++ b/hw/virtio-net.c
> @@ -122,8 +122,7 @@ static uint32_t virtio_net_get_features(VirtIODevice *vdev)
>                          (1 << VIRTIO_NET_F_STATUS) |
>                          (1 << VIRTIO_NET_F_CTRL_VQ) |
>                          (1 << VIRTIO_NET_F_CTRL_RX) |
> -                        (1 << VIRTIO_NET_F_CTRL_VLAN) |
> -                        (1 << VIRTIO_NET_F_CTRL_RX_EXTRA);
> +                        (1 << VIRTIO_NET_F_CTRL_VLAN);
>  
>      return features;
>  }
> diff --git a/hw/virtio-net.h b/hw/virtio-net.h
> index 2085181..9bc4210 100644
> --- a/hw/virtio-net.h
> +++ b/hw/virtio-net.h
> @@ -43,7 +43,6 @@
>  #define VIRTIO_NET_F_CTRL_VQ    17      /* Control channel available */
>  #define VIRTIO_NET_F_CTRL_RX    18      /* Control channel RX mode support */
>  #define VIRTIO_NET_F_CTRL_VLAN  19      /* Control channel VLAN filtering */
> -#define VIRTIO_NET_F_CTRL_RX_EXTRA 20   /* Extra RX mode control support */
>  
>  #define VIRTIO_NET_S_LINK_UP    1       /* Link is up */
>  
> @@ -106,9 +105,10 @@ typedef uint8_t virtio_net_ctrl_ack;
>  /*
>   * Control the RX mode, ie. promisucous, allmulti, etc...
>   * All commands require an "out" sg entry containing a 1 byte
> - * state value, zero = disable, non-zero = enable.  Commands
> - * 0 and 1 are supported with the VIRTIO_NET_F_CTRL_RX feature.
> - * Commands 2-5 are added with VIRTIO_NET_F_CTRL_RX_EXTRA.
> + * state value, zero = disable, non-zero = enable.  This group
> + * of commands are available with the VIRTIO_NET_F_CTRL_RX
> + * feature.  Individual commands may return VIRTIO_NET_ERR if
> + * unsupported by the host.
>   */
>  #define VIRTIO_NET_CTRL_RX_MODE    0
>   #define VIRTIO_NET_CTRL_RX_MODE_PROMISC      0
> 
> 

  reply	other threads:[~2009-06-14  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 19:17 [Qemu-devel] [PATCH] virtio-net: Remove RX_EXTRA feature Alex Williamson
2009-06-14  9:39 ` Michael S. Tsirkin [this message]
2009-06-14 13:31   ` Alex Williamson
2009-06-15  5:18     ` Rusty Russell
2009-06-15 14:45       ` Alex Williamson
2009-06-16  3:19         ` Rusty Russell
2009-06-16 14:29           ` Alex Williamson

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=20090614093954.GB6959@redhat.com \
    --to=mst@redhat.com \
    --cc=alex.williamson@hp.com \
    --cc=markmc@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    /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).