On Thu, Aug 25, 2011 at 08:24:09AM -0500, Brian King wrote: > > Is this broken ATM? I thought the PCI core would simply try all methods > > + has a quirks section for completely funky devices. > > Yes. Its certainly broken for ipr. If the ipr driver is loaded, it really needs > to be the one doing the reset. If its not loaded, I may need to add a few > quirks for these adapters to properly handle this function. > > -Brian Driving reset through sysfs while another driver is bound is likely broken for many types of devices. But so it writing config space through sysfs, or accessing BARs by mmap while a kernel driver is bound with the exception of simple stub drivers such as uio and pci-stub. And no amount of locking can fix that I think. Let's try to see whether there's an issue with existing applications, all of which IIUC have a single userspace driver accessing the device. Besides that, all we need to address, as I see it, is not making things worse: that is if device potentially gets broken by a sysfs access, we can't help this, but let's at least not trigger BUG errors. -- MST -- 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
