qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org,
	Sriram Yagnaraman <sriram.yagnaraman@est.tech>,
	 Akihiko Odaki <akihiko.odaki@daynix.com>,
	Dmitry Fleytman <dmitry.fleytman@gmail.com>
Subject: Re: [PATCH v2 1/2] igb: fix link state on resume
Date: Thu, 1 Feb 2024 13:45:20 +0800	[thread overview]
Message-ID: <CACGkMEuijE=r_AavGpCDgsbFx42czcFHkLcadZXmJ7os2YGuBg@mail.gmail.com> (raw)
In-Reply-To: <20240124102904.334595-1-lvivier@redhat.com>

On Wed, Jan 24, 2024 at 6:30 PM Laurent Vivier <lvivier@redhat.com> wrote:
>
> On resume igb_vm_state_change() always calls igb_autoneg_resume()
> that sets link_down to false, and thus activates the link even
> if we have disabled it.
>
> The problem can be reproduced starting qemu in paused state (-S) and
> then set the link to down. When we resume the machine the link appears
> to be up.
>
> Reproducer:
>
>    # qemu-system-x86_64 ... -device igb,netdev=netdev0,id=net0 -S
>
>    {"execute": "qmp_capabilities" }
>    {"execute": "set_link", "arguments": {"name": "net0", "up": false}}
>    {"execute": "cont" }
>
> To fix the problem, merge the content of igb_vm_state_change()
> into igb_core_post_load() as e1000 does.
>
> Buglink: https://issues.redhat.com/browse/RHEL-21867
> Fixes: 3a977deebe6b ("Intrdocue igb device emulation")
> Cc: akihiko.odaki@daynix.com
> Suggested-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
>
> Notes:
>     v2: Add Fixes: and a comment about igb_intrmgr_resume() purpose.
>

Queued.

Thanks



      parent reply	other threads:[~2024-02-01  5:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 10:29 [PATCH v2 1/2] igb: fix link state on resume Laurent Vivier
2024-01-28 11:36 ` Akihiko Odaki
2024-02-01  5:45 ` Jason Wang [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='CACGkMEuijE=r_AavGpCDgsbFx42czcFHkLcadZXmJ7os2YGuBg@mail.gmail.com' \
    --to=jasowang@redhat.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=dmitry.fleytman@gmail.com \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sriram.yagnaraman@est.tech \
    /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).