From: Amos Kong <akong@redhat.com>
To: qemu-devel@nongnu.org
Cc: jasowang@redhat.com, mst@redhat.com, Amos Kong <akong@redhat.com>,
stefanha@linux.vnet.ibm.com, aliguori@us.ibm.com
Subject: [Qemu-devel] [PATCH v4 3/3] update nc.link_down in virtio_net_load()
Date: Mon, 17 Sep 2012 10:25:36 +0800 [thread overview]
Message-ID: <1347848736-25194-4-git-send-email-akong@redhat.com> (raw)
In-Reply-To: <504DA1A9.2000908@redhat.com>
nc.link_down could not be migrated, this patch updates link_down in
virtio_post_load() to keep it coincident with real link status.
Signed-off-by: Amos Kong <akong@redhat.com>
---
hw/virtio-net.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/hw/virtio-net.c b/hw/virtio-net.c
index b1998b2..e637619 100644
--- a/hw/virtio-net.c
+++ b/hw/virtio-net.c
@@ -977,6 +977,10 @@ static int virtio_net_load(QEMUFile *f, void *opaque, int version_id)
}
}
n->mac_table.first_multi = i;
+
+ /* infer link_down according to link status bit in n->status */
+ n->nic->nc.link_down = (n->status & VIRTIO_NET_S_LINK_UP) == 0;
+
return 0;
}
--
1.7.1
prev parent reply other threads:[~2012-09-17 2:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 7:59 [Qemu-devel] [PATCH] rtl8139: implement 8139cp link status Amos Kong
2012-09-10 8:15 ` Jason Wang
2012-09-13 8:48 ` Jason Wang
2012-09-13 8:51 ` [Qemu-devel] [PATCH v2] " Amos Kong
2012-09-13 12:29 ` Stefan Hajnoczi
2012-09-14 1:34 ` Amos Kong
2012-09-14 7:30 ` Stefan Hajnoczi
2012-09-14 9:01 ` Jason Wang
2012-09-14 2:16 ` [Qemu-devel] [PATCH v3] " Amos Kong
2012-09-14 8:36 ` Paolo Bonzini
2012-09-14 9:20 ` Amos Kong
2012-09-17 2:25 ` [Qemu-devel] [PATCH v4 0/3] net: fix " Amos Kong
2012-09-17 2:44 ` Jason Wang
2012-09-17 2:25 ` [Qemu-devel] [PATCH v4 1/3] rtl8139: implement 8139cp " Amos Kong
2012-09-27 9:30 ` Stefan Hajnoczi
2012-09-17 2:25 ` [Qemu-devel] [PATCH v4 2/3] e1000: update nc.link_down in e1000_post_load() Amos Kong
2012-09-17 2:25 ` Amos Kong [this message]
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=1347848736-25194-4-git-send-email-akong@redhat.com \
--to=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).