Re: [PATCH RFC] virtio-pci: new config layout: using memory BAR

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anthony Liguori <aliguori@xxxxxxxxxx> writes:
> Hi Rusty,
>
> Rusty Russell <rusty@xxxxxxxxxxxxxxx> writes:
>
>> Anthony Liguori <aliguori@xxxxxxxxxx> writes:
>>> 4) Do virtio-pcie, make it PCI-e friendly (drop the IO BAR completely), give
>>>    it a new device/vendor ID.   Continue to use virtio-pci for existing
>>>    devices potentially adding virtio-{net,blk,...}-pcie variants for
>>>    people that care to use them.
>>
>> Now you have a different compatibility problem; how do you know the
>> guest supports the new virtio-pcie net?
>
> We don't care.
>
> We would still use virtio-pci for existing devices.  Only new devices
> would use virtio-pcie.

My concern is that new features make the virtio-pcie driver so desirable
that libvirt is pressured to use it ASAP.  Have we just punted the
problem upstream?

(Of course, feature bits were supposed to avoid such a transition issue,
but mistakes accumulate).

Cheers,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux