On Wed, 2010-07-28 at 14:14 -0700, Tom Lyon wrote: > On Tuesday, July 27, 2010 04:53:22 pm Michael S. Tsirkin wrote: > > On Tue, Jul 27, 2010 at 03:13:14PM -0700, Tom Lyon wrote: > > > [ Sorry for the long hiatus, I've been wrapped up in other issues.] > > > > > > I think the fundamental issue to resolve is to decide on the model which > > > the VFIO driver presents to its users. > > > > > > Fundamentally, VFIO as part of the OS must protect the system from its > > > users and also protect the users from each other. No disagreement here. > > > > > > But another fundamental purpose of an OS to to present an abstract model > > > of the underlying hardware to its users, so that the users don't have to > > > deal with the full complexity of the hardware. > > > > > > So I think VFIO should present a 'virtual', abstracted PCI device to its > > > users whereas Michael has argued for a simpler model of presenting the > > > real PCI device config registers while preventing writes only to the > > > registers which would clearly disrupt the system. > > > > In fact, there is no contradiction. I am all for an abstracted > > API *and* I think the virtualization concept is a bad way > > to build this API. > > > > The 'virtual' interface you present is very complex and hardware specific: > > you do not hide literally *anything*. Deciding which functionality > > userspace needs, and exposing it to userspace as a set of APIs would be > > abstract. Instead you ask people to go read the PCI spec, the device spec, > > and bang on PCI registers, little-endian-ness and all, then try to > > interpret what do the virtual values mean. > > Exactly! The PCI bus is far better *specified*, *documented*, and widely > implemented than a Linux driver could ever hope to be. And there are lots of > current Linux drivers which bang around in pci config space simply because the > authors were not aware of some api call buried deep in linux which would do > the work for them - or - got tired of using OS-specific APIs when porting a > driver and decided to just ask the hardware. > > > Example: > > > > How do I find # of MSI-X vectors? Sure, scan the capability list, > > find the capability, read the value, convert from little endian > > at each step. > > A page or two of code, and let's hope I have a ppc to test on. > > And note no driver has this code - they all use OS routines. > > > > So why wouldn't > > ioctl(dev, VFIO_GET_MSIX_VECTORS, &n); > > better serve the declared goal of presenting an abstracted PCI device to > > users? > > By and large, the user drivers just know how many because the hardware is > constant. Something like GET_MSIX_VECTORS seems like a user library routine to me. The PCI config space is well specified and if we try to do more than shortcut trivial operations (like getting the BAR length), we risk losing functionality. And for my purposes, translating to and from a made up API to PCI for the guest seems like a pain. > And inventing 20 or 30 ioctls to do a bunch of random stuff is gross when you > can instead use normal read and write calls to a well defined structure. Yep, this sounds like a job for libvfio. > > > Now, the virtual model *could* look little like the real hardware, and > > > use bunches of ioctls for everything it needs, > > > > Or reads/writes at special offsets, or sysfs attributes. > > > > > or it could look a lot like PCI and > > > use reads and writes of the virtual PCI config registers to trigger its > > > actions. The latter makes things more amenable to those porting drivers > > > from other environments. > > > > I really doubt this helps at all. Drivers typically use OS-specific > > APIs. It is very uncommon for them to touch standard registers, > > which is 100% of what your patch seem to be dealing with. > > > > And again, how about a small userspace library that would wrap vfio and > > add the abstractions for drivers that do need them? > > Yes, there will be userspace libraries - I already have a vfio backend for > libpci. > > > > > I realize that to date the VFIO driver has been a bit of a mish-mash > > > between the ioctl and config based techniques; I intend to clean that > > > up. And, yes, the abstract model presented by VFIO will need plenty of > > > documentation. > > > > And, it will need to be maintained forever, bugs and all. > > For example, if you change some register you emulated > > to fix a bug, to the driver this looks like a hardware change, > > and it will crash. > > The changes will come only to allow for a more-perfect emulation, so I doubt > that will cause driver problems. No different than discovering and fixing > bugs in the ioctls needed in you scenario. > > > > > The PCI spec has some weak versioning support, but it > > is mostly not a problem in that space: a specific driver needs to > > only deal with a specific device. We have a generic driver so PCI > > configuration space is a bad interface to use. > > PCI has great versioning. Damn near every change made in 16+ years has been > upwards compatible. BIOS and OS writers don't have trouble with generic PCI, > why should vfio? > > > > > > Since KVM/qemu already has its own notion of a virtual PCI device which > > > it presents to the guest OS, we either need to reconcile VFIO and qemu, > > > or provide a bypass of the VFIO virtual model. This could be direct > > > access through sysfs, or else an ioctl to VFIO. Since I have no > > > internals knowledge of qemu, I look to others to choose. > > > > Ah, so there will be 2 APIs, one for qemu, one for userspace drivers? > > I hope not, but I also hope not to become the qemu expert to find out. Alex > W. seemed to be making progress in this area. I hope not too, the qemu driver I wrote does perfectly fine with the virtualized config space (aside from things like guest initiated FLR or resent via oem specific mechanism, which we need to figure out how to handle anway). I end up calling into the qemu PCI emulation for writes only to keep the qemu infrastructure working when BARs get mapped. Reads come from VFIO except for the command register due to the mem/io bits not necessarily tracking what the driver expects for VFs. The old device assignment driver uses pci sysfs, so I think we can easily adapt the qemu vfio driver in either direction, virtualized config space or non. I do prefer the virtualized config space because it makes my life easier in the qemu vfio driver. I have far, far fewer traps for reads and writes to specific addresses than the old device assignment driver. Thanks, Alex > > > Other little things: > > > 1. Yes, I can share some code with sysfs if I can get the right EXPORTs > > > there. 2. I'll add multiple MSI support, but I wish to point out that > > > even though the PCI MSI API supports it, none of the architectures do. > > > 3. FLR needs work. I was foolish enough to assume that FLR wouldn't > > > reset BARs; now I know better. > > > > And as I said separately, drivers might reset BARs without FLR as well. > > As long as io/memory is disabled, we really should allow userspace > > write anything in BARs. And once we let it do it, most of the problem goes > > away. > > > > > 4. I'll get rid of the vfio config_map in sysfs; it was there for > > > debugging. 5. I'm still looking to support hotplug/unplug and power > > > management stuff via generic netlink notifications. > -- > 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 -- 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
