On Thu, 2015-04-02 at 14:09 +0200, Michael S. Tsirkin wrote: > On Thu, Apr 02, 2015 at 01:23:06AM -0700, Christoph Hellwig wrote: > > The class ids are a hardware defintion, not a kernel API. > > It's part of the API, it's used to decode values in this sysfs file: > /sys/bus/pci/devices/<address>/class > VFIO also made this part of it's kernel API. vfio-pci does expose PCI config space, but it also exposes memory mapped and io port mapped regions of the device. Do we consider the memory mapped config space of every device that can be exposed through vfio to be part of the kernel API? I don't think so. PCI config space is obviously more standardized and vfio-pci plays a greater role in intercepting and interacting with standardized portions, but we don't really care where userspace gets their definitions for config space offsets. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
