Tuesday, July 8, 2014, 8:58:22 PM, you wrote: > These patches had been posted in the past and had been reworked > to address reviews. The original concerns with the patches was > the complex logic of doing an workqueue (or thread) that would > do the FLR/bus/slot reset outside the PCI lock. That idea proved > buggy. The other idea of usurping the 'reset' SysFS didn't work > either - as the the generic code will complain loudly about this.
> The best so far mechanism is to use the 'xl' toolstack usage > of 'do_flr' and make that work in Xen pciback. > Documentation/ABI/testing/sysfs-driver-pciback | 95 ++++++++++++++ > drivers/xen/xen-pciback/pci_stub.c | 163 > +++++++++++++++++++----- > drivers/xen/xen-pciback/xenbus.c | 2 +- > 3 files changed, 224 insertions(+), 36 deletions(-) > Konrad Rzeszutek Wilk (7): > xen-pciback: Document the various parameters and attributes in SysFS > xen/pciback: Don't deadlock when unbinding. > xen/pciback: Move the FLR code to a function. > xen/pciback: Implement PCI reset slot or bus with 'do_flr' SysFS > attribute > xen/pciback: Include the domain id if removing the device whilst still > in use > xen/pciback: Print out the domain owning the device. > xen/pciback: Remove tons of dereferences Could you push these to your kernel.org git tree ? -- Sander -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
