Re: [PATCH] Assign the correct pci id range to virtio_pci

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

 



On Mon, 27 Apr 2009 12:53:25 pm Pantelis Koukousoulas wrote:
> On Mon, Apr 27, 2009 at 3:44 AM, Anthony Liguori <anthony@xxxxxxxxxxxxx> wrote:
> > Would be good to at least include the "experiment range" in case people are
> > making third-party virtio modules and want to play around without replacing
> > virtio-{pci,*}.
> 
> I 'd be happy with a simple comment explaining the 0x103f (e.g.,
> /* Not yet using the full 0x1000 - 0x10ef to hedge our bets in case we
> broke the ABI.*/
> as explained above)

Thanks, I like your patch.

Where did this idea of "experimental" range come from, BTW?  I prefer your
module cmdline approach, as it discourages deployment with such numbers.

Thanks,
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