From: pradeep <psuriset@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
Jes.Sorensen@redhat.com, jasowang@redhat.com,
qemu-devel@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>,
Sridhar Samudrala <samudrala.sridhar@gmail.com>
Subject: [Qemu-devel] Re: [PATCH] vhost: disable on tap link down
Date: Tue, 8 Feb 2011 17:40:58 +0530 [thread overview]
Message-ID: <20110208174058.71d73062@skywalker> (raw)
In-Reply-To: <20110207135001.GA23844@redhat.com>
On Mon, 7 Feb 2011 15:50:01 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> qemu makes it possible to disable link at tap
> which is not communicated to the guest but
> causes all packets to be dropped.
>
> Handle this with vhost simply by moving to the userspace emulation.
>
> Note: it might be a good idea to make peer link status match
> tap in this case, so the guest gets an event
> and updates the carrier state. For now
> stay bug for bug compatible with what we used to have.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> Reported-by: pradeep <psuriset@linux.vnet.ibm.com>
> ---
>
> Untested.
> Pradeep, mind trying this patch out and reporting?
Hi mst
This patch works. Thanks
--Pradeep
> Thanks!
>
> hw/virtio-net.c | 4 ++++
> net.c | 7 +++++++
> 2 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/hw/virtio-net.c b/hw/virtio-net.c
> index 671d952..fc2d6f5 100644
> --- a/hw/virtio-net.c
> +++ b/hw/virtio-net.c
> @@ -112,6 +112,10 @@ static void virtio_net_vhost_status(VirtIONet
> *n, uint8_t status) return;
> }
>
> + if (n->nic->nc.peer->link_down) {
> + return;
> + }
> +
> if (!tap_get_vhost_net(n->nic->nc.peer)) {
> return;
> }
> diff --git a/net.c b/net.c
> index 9ba5be2..57ee997 100644
> --- a/net.c
> +++ b/net.c
> @@ -1324,6 +1324,13 @@ done:
> if (vc->info->link_status_changed) {
> vc->info->link_status_changed(vc);
> }
> +
> + /* Notify peer. Don't update peer link status: this makes it
> possible to
> + * disconnect from host network without notifying the guest.
> + * FIXME: is this useful? Could just be an artifact of vlan
> support. */
> + if (vc->peer && vc->peer->info->link_status_changed) {
> + vc->peer->info->link_status_changed(vc->peer);
> + }
> return 0;
> }
>
next prev parent reply other threads:[~2011-02-08 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 13:50 [Qemu-devel] [PATCH] vhost: disable on tap link down Michael S. Tsirkin
2011-02-08 12:10 ` pradeep [this message]
2011-02-08 15:41 ` [Qemu-devel] " Michael S. Tsirkin
2011-02-10 13:21 ` pradeep
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=20110208174058.71d73062@skywalker \
--to=psuriset@linux.vnet.ibm.com \
--cc=Jes.Sorensen@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=samudrala.sridhar@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).