From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
Cc: Siwei Liu <loseweigh@gmail.com>,
Cornelia Huck <cohuck@redhat.com>,
si-wei liu <si-wei.liu@oracle.com>,
Roman Kagan <rkagan@virtuozzo.com>,
Venu Busireddy <venu.busireddy@oracle.com>,
Marcel Apfelbaum <marcel@redhat.com>,
virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org,
Alexander Duyck <alexander.h.duyck@intel.com>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [Qemu-devel] [virtio-dev] Re: [PATCH v3 0/3] Use of unique identifier for pairing virtio and passthrough devices...
Date: Fri, 13 Jul 2018 06:28:39 +0300 [thread overview]
Message-ID: <20180713062755-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <77823ff9-a02a-808b-e919-b4950a64ae3c@intel.com>
On Thu, Jul 12, 2018 at 09:20:41PM -0400, Samudrala, Sridhar wrote:
> On 7/12/2018 6:19 PM, Siwei Liu wrote:
> > On Thu, Jul 12, 2018 at 2:00 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > > On Thu, Jul 12, 2018 at 01:52:53PM -0700, Siwei Liu wrote:
> > > > The definition is incomplete due to lack of spec. There's no "host"
> > > > part defined yet in the host-guest interface. If match by MAC is an
> > > > interface, the same must be done on the host(device) side as well,
> > > > which has been agreed not the way to go. However, I don't think that's
> > > > what the author intends to do by interpreting his QEMU patch - it
> > > > missed the other parts as well, such as the feature negotiation and
> > > > how it interacts with the paired device.
> > > >
> > > > What I said is that match by MAC is just a guest implementation that
> > > > one can change at any time. We now have the group ID on QEMU, why
> > > > still sticking to matching by MAC? It shoulnd't be a host-guest
> > > > interface in the first place anyway.
> > > I think that match by MAC is a simple portable way to match devices.
> > > E.g. it will work seamlessly with niche things like zPCI. However
> > That's a good point. I'm not sure if it's a valid assumption that zPCI
> > should always use the same MAC address as that of virtio. Someone
> > who's more familiar with the use case may decide and work on that. It
> > means VFIO device has to take in the MAC address as an identifier to
> > the "-device vfio-pci,.." QEMU option. I think there's no point to
> > match device using group ID in QEMU while using MAC in the guest.
> > Based on that assumption, I'd go with making VIRTIO_NET_F_STANDBY to
> > match device based on group ID, while someone may come up with another
> > feature bit later, say VIRTIO_NET_F_STANDBY_BY_MAC when its QEMU
> > support is available. Would it make sense?
>
> VIRTIO_NET_F_STANDBY as defined in the guest virtio_net driver supports match
> by MAC address. I think we should add support for this feature bit in QEMU.
> If submitting a patch to update the spec is a pre-requisite to add this
> feature bit to QEMU, i can do that.
It's not strictly a prerequisite but we need it in spec all the same, so
pls do that.
> As far as i understand, group id patches to QEMU are still under review.
> Matching by group ID can be another feature bit that could support matching
> by group id as well as MAC.
>
>
> > -Siwei
> >
> > > there are other niche use-cases that aren't addressed by match by MAC
> > > such as PF pass-through as a primary, and the pci bridge trick addresses
> > > that at cost of some portability.
> > >
> > > So I see no issues supporting both mechanisms, but others on the TC
> > > might feel differently.
> > >
> > > --
> > > MST
next prev parent reply other threads:[~2018-07-13 3:28 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 22:19 [Qemu-devel] [PATCH v3 0/3] Use of unique identifier for pairing virtio and passthrough devices Venu Busireddy
2018-06-29 22:19 ` [Qemu-devel] [PATCH v3 1/3] Add "Group Identifier" support to virtio devices Venu Busireddy
2018-06-29 22:19 ` [Qemu-devel] [PATCH v3 2/3] Add "Group Identifier" support to Red Hat PCI bridge Venu Busireddy
2018-07-03 3:13 ` [Qemu-devel] [virtio-dev] " Siwei Liu
2018-06-29 22:19 ` [Qemu-devel] [PATCH v3 3/3] Add "Group Identifier" support to Red Hat PCI Express bridge Venu Busireddy
2018-07-07 12:14 ` [Qemu-devel] [virtio-dev] " Marcel Apfelbaum
2018-07-31 15:58 ` Venu Busireddy
2018-07-31 16:03 ` Michael S. Tsirkin
2018-07-31 19:11 ` Marcel Apfelbaum
2018-06-29 22:19 ` [Qemu-devel] [PATCH v3 virtio 1/1] Add "Group Identifier" to virtio PCI capabilities Venu Busireddy
2018-07-02 16:14 ` [Qemu-devel] [PATCH v3 0/3] Use of unique identifier for pairing virtio and passthrough devices Roman Kagan
2018-07-02 21:14 ` si-wei liu
2018-07-03 9:58 ` Roman Kagan
2018-07-03 14:28 ` Venu Busireddy
2018-07-03 14:52 ` [Qemu-devel] [virtio-dev] " Cornelia Huck
2018-07-03 23:31 ` Siwei Liu
2018-07-04 12:15 ` Cornelia Huck
2018-07-06 0:49 ` Siwei Liu
2018-07-06 13:54 ` Cornelia Huck
2018-07-06 15:07 ` Michael S. Tsirkin
2018-07-09 16:20 ` Cornelia Huck
2018-07-06 23:37 ` Siwei Liu
2018-07-09 16:27 ` Cornelia Huck
2018-07-09 13:14 ` Roman Kagan
2018-07-09 16:10 ` Cornelia Huck
2018-07-03 15:34 ` [Qemu-devel] " Roman Kagan
2018-07-03 22:27 ` si-wei liu
2018-07-09 13:00 ` Roman Kagan
2018-07-09 18:35 ` Michael S. Tsirkin
2018-07-10 1:11 ` si-wei liu
2018-07-10 1:54 ` Michael S. Tsirkin
2018-07-11 0:07 ` [Qemu-devel] [virtio-dev] " Siwei Liu
2018-07-11 9:53 ` Cornelia Huck
2018-07-12 9:37 ` Siwei Liu
2018-07-12 11:31 ` Cornelia Huck
2018-07-12 20:52 ` Siwei Liu
2018-07-12 21:00 ` Michael S. Tsirkin
2018-07-12 22:19 ` Siwei Liu
2018-07-13 1:20 ` Samudrala, Sridhar
2018-07-13 3:28 ` Michael S. Tsirkin [this message]
2018-07-13 9:15 ` Cornelia Huck
2018-07-12 19:18 ` Michael S. Tsirkin
2018-07-10 1:58 ` [Qemu-devel] " Michael S. Tsirkin
2018-07-10 18:56 ` [Qemu-devel] [virtio-dev] " Siwei Liu
2018-07-10 2:05 ` [Qemu-devel] " Michael S. Tsirkin
2018-07-04 5:43 ` Michael S. Tsirkin
2018-07-10 2:11 ` Michael S. Tsirkin
2018-07-10 14:28 ` Venu Busireddy
2018-07-12 21:01 ` 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=20180713062755-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=cohuck@redhat.com \
--cc=loseweigh@gmail.com \
--cc=marcel@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=si-wei.liu@oracle.com \
--cc=sridhar.samudrala@intel.com \
--cc=venu.busireddy@oracle.com \
--cc=virtio-dev@lists.oasis-open.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).