qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: aliguori@us.ibm.com, Amos Kong <akong@redhat.com>,
	mst@redhat.com, qemu-devel@nongnu.org,
	stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2] rtl8139: implement 8139cp link status
Date: Fri, 14 Sep 2012 17:01:43 +0800	[thread overview]
Message-ID: <5052F277.7000703@redhat.com> (raw)
In-Reply-To: <CAJSP0QVg6u62V82rEhWzhsMQto_kVN=n0u4B3wPP0JcAKXkKtw@mail.gmail.com>

On 09/14/2012 03:30 PM, Stefan Hajnoczi wrote:
> On Fri, Sep 14, 2012 at 2:34 AM, Amos Kong<akong@redhat.com>  wrote:
>> On 13/09/12 20:29, Stefan Hajnoczi wrote:
>>> On Thu, Sep 13, 2012 at 9:51 AM, Amos Kong<akong@redhat.com>  wrote:
>>> Regarding migration: do we migrate the NetClient->link_down field? If
>>> we only migrate the status register value then the link may actually
>>> be up at the net.c level.
>>
>> I tried to add 'MediaStatus' to 'struct RTL8139State', and update
>> 'VMStateDescription vmstate_rtl8139', then the value of MediaStatus
>> will be migrated.
>>
>> But the idea in v2 is better.
> Migrating the NIC's media status is not enough.  Above I asked about
> migrating nc->link_down, which determines whether net.c delivers
> packets or drops them.
>
> Your patch migrates the NIC's media status but I believe nc->link_down
> isn't being migrated and the guest will therefore receive packets from
> the host!  This could lead to unexpected results since the guest
> thinks the link is down.
>
> It's not a bug in your patch, but a larger issue that needs to be
> addressed for all NICs that support migration.  (Unless I missed the
> code that will migrate link_down.)
>
> Stefan

A possible solution is to infer the nc->link_down from the media status 
register in the destination. It works without adding more codes net.c 
but need model specific callback functions.

  reply	other threads:[~2012-09-14  8:58 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 [this message]
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   ` [Qemu-devel] [PATCH v4 3/3] update nc.link_down in virtio_net_load() Amos Kong

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=5052F277.7000703@redhat.com \
    --to=jasowang@redhat.com \
    --cc=akong@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --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).