qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: jasowang@redhat.com, mst@redhat.com, aliguori@us.ibm.com,
	stefanha@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] rtl8139: implement 8139cp link status
Date: Fri, 14 Sep 2012 17:20:24 +0800	[thread overview]
Message-ID: <5052F6D8.2050402@redhat.com> (raw)
In-Reply-To: <5052EC74.7000803@redhat.com>

On 14/09/12 16:36, Paolo Bonzini wrote:
> Il 14/09/2012 04:16, Amos Kong ha scritto:
>> +            /* The LinkDown bit of MediaStatus is inverse with link status */
>> +            ret = 0xd0 | (s->nic->nc.link_down ? MSR_LinkDown : 0);
>>               DPRINTF("MediaStatus read 0x%x\n", ret);
>>               break;
>>
>> @@ -3453,12 +3466,27 @@ static void pci_rtl8139_uninit(PCIDevice *dev)
>>       qemu_del_net_client(&s->nic->nc);
>>   }
>>
>> +static void rtl8139_set_link_status(NetClientState *nc)
>> +{
>> +    RTL8139State *s = DO_UPCAST(NICState, nc, nc)->opaque;
>> +
>> +    if (nc->link_down) {
>> +        s->BasicModeStatus &= ~0x0004;
>> +    } else {
>> +        s->BasicModeStatus |= 0x0004;
>> +    }
>> +
>> +    s->IntrStatus |= RxUnderrun;
>> +    rtl8139_update_irq(s);
>> +}
>> +
>
> Actually, this is worse than v2 because then one bit is migrated and the
> other is not.

> I think v2 is correct and, on top of it, you have to check in post_load
> whether nc->link_down matches the loaded BMSR value.  If not, you need
> to either set the link status in NetClientState, or generate an
> RxUnderrun interrupt.


If correct link_down in rtl8139_post_load(), both v2 and v3 will work.

   s->nic->nc.link_down = (s->BasicModeStatus & 0x04) == 0;

s->BasicModeStatus is really migrated, s->nic->nc.link_down is inferred.
so I will continually work on v2.


> An alternative is to add a get_link_status callback and call it after
> migration for all NIC NetClientStates.
>
> Paolo

Thanks.

-- 
			Amos.

  reply	other threads:[~2012-09-14  9:20 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 [this message]
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=5052F6D8.2050402@redhat.com \
    --to=akong@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).