From: Rajat Jain <rajatjain.linux@gmail.com>
To: Linux-PCI <linux-pci@vger.kernel.org>,
Linux-hotplug <linux-hotplug@vger.kernel.org>,
linux-kernel@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
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.linux@gmail.com>,
Rajat Jain <rajatjain@juniper.net>,
Guenter Roeck <groeck@juniper.net>
Subject: [RFC PATCH 0/4] Allow Link state changes for Hot-Plug
Date: Tue, 19 Nov 2013 22:39:50 +0000 [thread overview]
Message-ID: <528BE8B6.9080007@gmail.com> (raw)
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
WARNING: multiple messages have this Message-ID (diff)
From: Rajat Jain <rajatjain.linux@gmail.com>
To: Linux-PCI <linux-pci@vger.kernel.org>,
Linux-hotplug <linux-hotplug@vger.kernel.org>,
linux-kernel@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
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.linux@gmail.com>,
Rajat Jain <rajatjain@juniper.net>,
Guenter Roeck <groeck@juniper.net>
Subject: [RFC PATCH 0/4] Allow Link state changes for Hot-Plug
Date: Tue, 19 Nov 2013 14:39:50 -0800 [thread overview]
Message-ID: <528BE8B6.9080007@gmail.com> (raw)
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
next reply other threads:[~2013-11-19 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 22:39 Rajat Jain [this message]
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-21 13:16 ` Rajat Jain
2013-11-22 4:36 ` Bjorn Helgaas
2013-11-22 4:36 ` Bjorn Helgaas
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=528BE8B6.9080007@gmail.com \
--to=rajatjain.linux@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.