On Tue, 2013-08-20 at 08:44 +1000, Benjamin Herrenschmidt wrote: > On Mon, 2013-08-19 at 14:20 -0600, Alex Williamson wrote: > > I try to handle the slot as opaque, only caring that the slot pointer > > matches, so I think our implementation is ok... so long as we only get > > one driver claiming to manage a slot, but that's not a vfio problem ;) > > Thanks, > > By why bother with slots ? Why do you even think about slots in that > context ? slots are a badly defined thing in our current PCI stack, > pretty much intricated with hotplug. I don't see why the reset semantics > would be tied to slots at all. See my other reply, hotplug presence detection and secondary bus resets don't just work. > The only case where it *might* make some sense (and even then ...) is if > you want to start exposing slot power control and PERST but that would > imply a pile of platform specific gunk anyway. But that platform specific gunk can be hidden away in the hotplug controller. We just need to be able to ask if it can reset a slot and tell it to do it. If it happens via a slot power control or a secondary bus reset, do we care? Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
