Re: [RFC PATCH 0/4] Allow Link state changes for Hot-Plug

[Bjorn Helgaas]

I haven't had a chance yet, sorry.

On Thu, Nov 21, 2013 at 6:16 AM, Rajat Jain <rajatjain.linux@xxxxxxxxx> wrote:
> Hello Bjorn / Folks,
>
> Was wondering if you got a chance to look at this patchset?
>
> Thanks & Best Regards,
>
> Rajat Jain
>
> On Tue, Nov 19, 2013 at 2:39 PM, Rajat Jain <rajatjain.linux@xxxxxxxxx> wrote:
>>
>> Hello,
>>
>> This patch set enables the use of PCI Express link up and link down events
>> for Hotplug or Unplug. The requirement of such a feature was originally
>> discussed here:
>>
>> http://www.spinics.net/lists/linux-pci/msg05783.html
>> http://www.spinics.net/lists/hotplug/msg05801.html
>>
>> Patch [1/4]: makes a function non-static for use by patch 2.
>> Patch [2/4]: Contains the bulk logic to allow link events to be used
>>              for hotplug and removal.
>> Patch [3/4]: Makes the pciehp_power_thread() lock free by making it
>>              look at a work info->req instead of slot->state.
>> Patch [4/4]: Introduce slot->hotplug_lock to serialize the hotplug
>>              operations.
>>
>> I'd appreciate if you could please review and provide me with any comments.
>>
>> Thanks,
>>
>> Rajat
>>
>> Rajat Jain (4):
>>   pciehp: Make check_link_active() non-static
>>   pciehp: Use link state change notifications for hot-plug and removal
>>   pciehp: Ensure all hotplug events are processed, even very fast ones.
>>   pciehp: Introduce hotplug_lock to serialize HP events on each slot
>>
>>  drivers/pci/hotplug/pciehp.h      |    6 ++
>>  drivers/pci/hotplug/pciehp_core.c |   10 +-
>>  drivers/pci/hotplug/pciehp_ctrl.c |  181 ++++++++++++++++++++++++++++++++++---
>>  drivers/pci/hotplug/pciehp_hpc.c  |   63 +++++++++----
>>  4 files changed, 229 insertions(+), 31 deletions(-)
>>
>> --
>> 1.7.9.5
>>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/