From: Mikhail Sennikovsky <mikhail.sennikovskii@cloud.ionos.com>
To: qemu-devel@nongnu.org, jasowang@redhat.com, stefanha@redhat.com,
mst@redhat.com, "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Mikhail Sennikovsky <mikhail.sennikovskii@cloud.ionos.com>
Subject: [PATCH v3] virtio-net: prevent offloads reset on migration
Date: Thu, 10 Oct 2019 14:11:14 +0200 [thread overview]
Message-ID: <1570709475-32073-1-git-send-email-mikhail.sennikovskii@cloud.ionos.com> (raw)
Hi all,
This is the third version of the patch, implementing the approach
based on checking the VM runstate proposed by Jason Wang.
Regards,
Mikhail
Mikhail Sennikovsky (1):
virtio-net: prevent offloads reset on migration
hw/net/virtio-net.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2019-10-10 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 12:11 Mikhail Sennikovsky [this message]
2019-10-10 12:11 ` [PATCH v3] virtio-net: prevent offloads reset on migration Mikhail Sennikovsky
2019-10-10 13:15 ` no-reply
2019-10-10 13:17 ` no-reply
2019-10-10 15:04 ` Michael S. Tsirkin
2019-10-10 15:58 ` Dr. David Alan Gilbert
2019-10-10 17:46 ` Michael S. Tsirkin
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=1570709475-32073-1-git-send-email-mikhail.sennikovskii@cloud.ionos.com \
--to=mikhail.sennikovskii@cloud.ionos.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).