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

Re: [Xen-devel] [PATCH 4/5] pciback: user-space quirks policy




On 27 Jul 2006, at 13:56, Chris wrote:

 2. It's a bit weird that xend-pci-quirks.sxp identifies devices by
vendor/device ids, but xend-pci-permissive.sxp identifies by slot. Could the latter also identify by vendor/device ids -- after all, the need to be in the list is a property of the device, not its position on the PCI
bus. This would also allow us to add devices to this list in a way
that's portable across systems (an idea I'm sure you hate ;-).

There was a method to my madness.  The goal was to make using devices
that require permissive mode possible, but to discourage its use as a
long-term solution, thereby encouraging admins to feed their quirky
device info back to xen-devel for a proper fix in xend-pci-permissive.sxp.

Yes, that was my suspicion. :-) Not unreasonable really as it shouldn't be hard to work out a quirks list for any given device, but I'd rather keep the same method of device identification across both config files.

By the way, your email didn't contain attachments but had a humungous blob of patch appended instead. Could you resend (all in one email is fine, but separate attachments) and remind me of the order in which to apply them? Thanks!

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.