From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
virtualization@lists.linux-foundation.org,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Sridhar Samudrala <sridhar.samudrala@intel.com>,
Achiad <achiad@mellanox.com>,
Peter Waskiewicz Jr <peter.waskiewicz.jr@intel.com>,
"Singhai, Anjali" <anjali.singhai@intel.com>,
Andy Gospodarek <gospo@broadcom.com>,
Or Gerlitz <gerlitz.or@gmail.com>,
Hannes Frederic Sowa <hannes@redhat.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [RFC] virtio-net: help live migrate SR-IOV devices
Date: Thu, 30 Nov 2017 16:14:37 +0200 [thread overview]
Message-ID: <20171130161125-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <0fb552d4-1bfc-e130-4fc1-87b83873916d@redhat.com>
On Thu, Nov 30, 2017 at 11:29:56AM +0800, Jason Wang wrote:
> If my understanding is correct there's no need to for any extension of
> virtio spec.
There appears to be a concern that some existing configurations
might use same MAC for an unrelated reason. Not sure what
that could be, but for sure, we could add a feature flag.
That needs to be approved by the virtio TC, but it's
just a single line in the spec no big deal, we can help here.
> If this is true, maybe you can start to prepare the patch?
Yes, please do. We can add a safeguard of a feature bit on top.
--
MST
prev parent reply other threads:[~2017-11-30 14:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171128112722.00003716@intel.com>
2017-11-30 3:29 ` [RFC] virtio-net: help live migrate SR-IOV devices Jason Wang
2017-11-30 3:51 ` Jakub Kicinski
2017-11-30 4:10 ` Stephen Hemminger
2017-11-30 4:21 ` Jakub Kicinski
2017-11-30 13:54 ` Michael S. Tsirkin
2017-11-30 20:48 ` Jakub Kicinski
2017-12-01 5:13 ` Michael S. Tsirkin
2017-11-30 8:08 ` achiad shochat
2017-11-30 14:11 ` Michael S. Tsirkin
2017-12-01 20:08 ` Shannon Nelson
2017-12-03 5:05 ` Michael S. Tsirkin
2017-12-03 9:14 ` achiad shochat
2017-12-03 17:35 ` Stephen Hemminger
2017-12-04 9:51 ` achiad shochat
2017-12-04 16:30 ` Alexander Duyck
2017-12-05 9:59 ` achiad shochat
2017-12-05 19:20 ` Michael S. Tsirkin
2017-12-05 21:52 ` Jesse Brandeburg
2017-12-05 22:05 ` Michael S. Tsirkin
2017-12-07 7:28 ` achiad shochat
2017-12-07 16:45 ` Alexander Duyck
2017-12-07 16:53 ` Michael S. Tsirkin
2017-12-05 22:29 ` Jakub Kicinski
2017-12-05 22:41 ` Stephen Hemminger
2017-11-30 14:14 ` Michael S. Tsirkin [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=20171130161125-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=achiad@mellanox.com \
--cc=anjali.singhai@intel.com \
--cc=gerlitz.or@gmail.com \
--cc=gospo@broadcom.com \
--cc=hannes@redhat.com \
--cc=jakub.kicinski@netronome.com \
--cc=jasowang@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.waskiewicz.jr@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=virtualization@lists.linux-foundation.org \
/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).