qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, jasowang@redhat.com, armbru@redhat.com,
	lcapitulino@redhat.com, alex.williamson@redhat.com,
	Amit Shah <amit.shah@redhat.com>,
	glommer@redhat.com
Subject: [Qemu-devel] [PATCHv3 0/2] vhost: fix tap link down
Date: Thu, 10 Feb 2011 13:33:23 +0800	[thread overview]
Message-ID: <19795.30883.336459.524149@gargle.gargle.HOWL> (raw)
In-Reply-To: <cover.1297269881.git.mst@redhat.com>

Michael S. Tsirkin writes:
 > qemu makes it possible to disable link at tap
 > which is not communicated to the guest but
 > causes all packets to be dropped.
 > 
 > With vhost-net at the moment it just keeps going.
 > Fix by communicating to virtio net and have that
 > stop vhost-net.
 > 
 > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
 > Reported-by: pradeep <psuriset@linux.vnet.ibm.com>
 > 
 > Changes from v2:
 > 	comment tweaked
 > 	split to two patches
 > 
 > Changes from v1:
 > 	fix link down after guest link is up
 > 
 > 
 > 
 > Michael S. Tsirkin (2):
 >   net: notify peer about link status change
 >   vhost: disable on tap link down
 > 
 >  hw/virtio-net.c |    3 ++-
 >  net.c           |   11 +++++++++++
 >  2 files changed, 13 insertions(+), 1 deletions(-)
 > 

Acked-by: Jason Wang <jasowang@redhat.com>

 > -- 
 > 1.7.3.2.91.g446ac
 > 

  parent reply	other threads:[~2011-02-10  5:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 16:44 [Qemu-devel] [PATCHv3 0/2] vhost: fix tap link down Michael S. Tsirkin
2011-02-09 16:45 ` [Qemu-devel] [PATCHv3 1/2] net: notify peer about link status change Michael S. Tsirkin
2011-02-09 16:45 ` [Qemu-devel] [PATCHv3 2/2] vhost: disable on tap link down Michael S. Tsirkin
2011-02-09 17:09 ` [Qemu-devel] Re: [PATCHv3 0/2] vhost: fix " Alex Williamson
2011-02-10  5:33 ` Jason Wang [this message]
2011-02-20 17:07 ` [Qemu-devel] " Aurelien Jarno

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=19795.30883.336459.524149@gargle.gargle.HOWL \
    --to=jasowang@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=glommer@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).