> -----Original Message----- > From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Friday, March 28, 2014 2:00 AM > To: Antonios Motakis > Cc: Yoder Stuart-B08248; alex.williamson@xxxxxxxxxx; > kvmarm@xxxxxxxxxxxxxxxxxxxxx; iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx; tech@xxxxxxxxxxxxxxxxxxxxxx; > a.rigo@xxxxxxxxxxxxxxxxxxxxxx; kim.phillips@xxxxxxxxxx; > jan.kiszka@xxxxxxxxxxx; kvm@xxxxxxxxxxxxxxx; Bhushan Bharat-R65777; Wood > Scott-B07421; christoffer.dall@xxxxxxxxxx; agraf@xxxxxxx; Sethi Varun- > B16395; will.deacon@xxxxxxx; Tejun Heo; Rafael J. Wysocki; Guenter Roeck; > Toshi Kani; Joe Perches; Dmitry Kasatkin; Michal Hocko; Bjorn Helgaas > Subject: Re: mechanism to allow a driver to bind to any device > > On Wed, Mar 26, 2014 at 10:39:57PM +0100, Antonios Motakis wrote: > > > > Of note is that new_id doesn't work particularly well for platform > devices. > > Nor should it. Platform devices suck horribly, and "ids" mean nothing > to them, so you shouldn't even try this. Use a "real" bus and it should > be fine. We have the hardware we have and have to live with it. A system-on-a-chip typically has bunches of memory mapped I/O devices that are not on a bus that supports probing. These devices don't have any discoverable device IDs. So, the Linux platform bus works fine for making Linux aware of these devices and associating drivers with them. Not sure why it is horrible. I don't see a reasonable alternative for dealing with these types of devices. But this is all besides the point of this thread, which encompasses PCI, platform bus, or any other kind of bus. This thread is about how specific devices can be bound to a vfio driver that wants to expose that device to user space. Stuart _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
