From: Bjorn Helgaas <bhelgaas@google.com>
To: Rajat Jain <rajatjain.linux@gmail.com>
Cc: Linux-PCI <linux-pci@vger.kernel.org>,
Linux-hotplug <linux-hotplug@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Alex Williamson <alex.williamson@redhat.com>,
Yijing Wang <wangyijing@huawei.com>,
Paul Bolle <pebolle@tiscali.nl>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Rajat Jain <rajatjain@juniper.net>,
Guenter Roeck <groeck@juniper.net>
Subject: Re: [RFC PATCH 0/4] Allow Link state changes for Hot-Plug
Date: Fri, 22 Nov 2013 04:36:51 +0000 [thread overview]
Message-ID: <CAErSpo64MDU2VTqgahoPecfzCjv1rK=sACDDdK8UMxgsqToDDQ@mail.gmail.com> (raw)
In-Reply-To: <CADTPrLS9iyvDkTLV5YyzJCiuGT2G0kTSbea8ZXzzT=E9RP71-Q@mail.gmail.com>
I haven't had a chance yet, sorry.
On Thu, Nov 21, 2013 at 6:16 AM, Rajat Jain <rajatjain.linux@gmail.com> 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@gmail.com> 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
>>
prev parent reply other threads:[~2013-11-22 4:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 22:39 [RFC PATCH 0/4] Allow Link state changes for Hot-Plug Rajat Jain
2013-11-21 13:16 ` Rajat Jain
2013-11-22 4:36 ` Bjorn Helgaas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAErSpo64MDU2VTqgahoPecfzCjv1rK=sACDDdK8UMxgsqToDDQ@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=alex.williamson@redhat.com \
--cc=ebiederm@xmission.com \
--cc=groeck@juniper.net \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pebolle@tiscali.nl \
--cc=rajatjain.linux@gmail.com \
--cc=rajatjain@juniper.net \
--cc=wangyijing@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).