netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Network Development <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Jason Wang <jasowang@redhat.com>,
	virtualization@lists.linux-foundation.org,
	Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next] virtio_net: implement VIRTIO_CONFIG_S_NEEDS_RESET
Date: Mon, 16 Oct 2017 18:31:23 +0300	[thread overview]
Message-ID: <20171016180442-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAF=yD-LdGiKuf=k2FDgFWbhvExVX8t+VVgTQetKTegjMeQ598g@mail.gmail.com>

On Mon, Oct 16, 2017 at 11:03:18AM -0400, Willem de Bruijn wrote:
> >> +static int virtnet_reset(struct virtnet_info *vi)
> >> +{
> >> +     struct virtio_device *dev = vi->vdev;
> >> +     int ret;
> >> +
> >> +     virtio_config_disable(dev);
> >> +     dev->failed = dev->config->get_status(dev) & VIRTIO_CONFIG_S_FAILED;
> >> +     virtnet_freeze_down(dev, true);
> >> +     remove_vq_common(vi);
> >> +
> >> +     virtio_add_status(dev, VIRTIO_CONFIG_S_ACKNOWLEDGE);
> >> +     virtio_add_status(dev, VIRTIO_CONFIG_S_DRIVER);
> >> +
> >> +     ret = virtio_finalize_features(dev);
> >> +     if (ret)
> >> +             goto err;
> >> +
> >> +     ret = virtnet_restore_up(dev);
> >> +     if (ret)
> >> +             goto err;
> >> +
> >> +     ret = virtnet_set_queues(vi, vi->curr_queue_pairs);
> >> +     if (ret)
> >> +             goto err;
> >> +
> >> +     virtio_add_status(dev, VIRTIO_CONFIG_S_DRIVER_OK);
> >> +     virtio_config_enable(dev);
> >> +     return 0;
> >> +
> >> +err:
> >> +     virtio_add_status(dev, VIRTIO_CONFIG_S_FAILED);
> >> +     return ret;
> >> +}
> >> +
> >>  static int virtnet_set_guest_offloads(struct virtnet_info *vi, u64 offloads)
> >>  {
> >>       struct scatterlist sg;
> >
> > I have a question here though. How do things like MAC address
> > get restored?
> >
> > What about the rx mode?
> >
> > vlans?
> 
> The function as is releases and reinitializes only ring state.
> Device configuration such as mac and vlan persist across
> the reset.

What gave you this impression? Take a look at e.g. this
code in qemu:

static void virtio_net_reset(VirtIODevice *vdev)
{   
    VirtIONet *n = VIRTIO_NET(vdev);
    
    /* Reset back to compatibility mode */
    n->promisc = 1;
    n->allmulti = 0;
    n->alluni = 0;
    n->nomulti = 0;
    n->nouni = 0;
    n->nobcast = 0;
    /* multiqueue is disabled by default */
    n->curr_queues = 1;
    timer_del(n->announce_timer);
    n->announce_counter = 0;
    n->status &= ~VIRTIO_NET_S_ANNOUNCE;
    
    /* Flush any MAC and VLAN filter table state */
    n->mac_table.in_use = 0; 
    n->mac_table.first_multi = 0; 
    n->mac_table.multi_overflow = 0;
    n->mac_table.uni_overflow = 0;
    memset(n->mac_table.macs, 0, MAC_TABLE_ENTRIES * ETH_ALEN);
    memcpy(&n->mac[0], &n->nic->conf->macaddr, sizeof(n->mac));
    qemu_format_nic_info_str(qemu_get_queue(n->nic), n->mac);
    memset(n->vlans, 0, MAX_VLAN >> 3);
}

So device seems to lose all state, you have to re-program it.


> > Also, it seems that LINK_ANNOUNCE requests will get ignored
> > even if they got set before the reset, leading to downtime.
> 
> Do you mean act on VIRTIO_NET_F_GUEST_ANNOUNCE
> requests? That flag is tested and netdev_notify_peers
> called before resetting virtio ring state.

Yes but I wonder if there's a race where announce
is set after it is read but before NEED_RESET is read.

Re-reading status from the config before reset
might be necessary.

-- 
MST

  reply	other threads:[~2017-10-16 15:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 15:51 [PATCH net-next] virtio_net: implement VIRTIO_CONFIG_S_NEEDS_RESET Willem de Bruijn
2017-10-15  0:45 ` Michael S. Tsirkin
2017-10-16 15:03   ` Willem de Bruijn
2017-10-16 15:31     ` Michael S. Tsirkin [this message]
2017-10-16 16:04       ` Willem de Bruijn
2017-10-16 16:38         ` Michael S. Tsirkin
2017-10-16 22:34           ` Willem de Bruijn
2017-10-17  3:05             ` Jason Wang
2017-10-17  3:44               ` Michael S. Tsirkin
2017-12-28 19:11                 ` Willem de Bruijn
2017-12-29  3:10                   ` 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=20171016180442-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=davem@davemloft.net \
    --cc=jasowang@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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).