OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [virtio-dev] [PATCH 0/1] Add "Group Identifier" to virtio PCI capabilities.


On 2018-06-01 23:03:16 +0300, Michael S. Tsirkin wrote:
> On Fri, Jun 01, 2018 at 12:01:26PM -0500, Venu Busireddy wrote:
> > On 2018-06-01 18:42:06 +0300, Michael S. Tsirkin wrote:
> > > On Wed, May 23, 2018 at 11:16:12AM -0400, Venu Busireddy wrote:
> > > > During live migration involving passthrough devices, the guest needs
> > > > to know which virtio device will be a fail-over device for a given
> > > > passthrough device.
> > > > 
> > > > Extending the virtio specification with a new "Group Identifier"
> > > > capability allows qemu to set up the grouping at the time the guest
> > > > is created. The "Group Identifier" can be as simple as a number, or an
> > > > UUID. The driver can use the group identifier to pair the virtio device
> > > > with the passthrough device. The passthrough device can contain the
> > > > group identifier in the PCIe bridge to which it is attached.
> > > > 
> > > > Venu Busireddy (1):
> > > >   Add "Group Identifier" to virtio PCI capabilities.
> > > > 
> > > >  content.tex | 43 +++++++++++++++++++++++++++++++++++++++++++
> > > >  1 file changed, 43 insertions(+)
> > > 
> > > Is this a PCI thing, or can this somehow be used with non-PCI
> > 
> > This is applicable to all virtio PCI devices, but not to non-PCI
> > devices.
> > 
> > > devices? If PCI, we can just add a PCI UUID capability to
> > > virtio without need to worry about the spec.
> > 
> > What is a "PCI UUID capability?" "PCI Local Bus Specification
> > Revision 3.0, Appendix H" does not list any such capability.
> > 
> > Regards,
> > 
> > Venu
> 
> Sorry that I'm unclear. What I meant is the
> PCI Express serial number capability (0003h).

0003h is the VPD capability. Serial Number ("SN") is part of the VPD. QEMU
does not support VPD, and adding the VPD capability to QEMU is lot more
involved than storing the UUID in Vendor-Specific capability.

Do you strongly believe that adding VPD is required? Or, can we live
with using Vendor-Specific capability? The bridge device is going to be
QEMU specific device anyway, so there should be no ambiguity of mixing
up with other bridges.

Thanks,

Venu



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]