From: Rajat Jain <rajatjain.linux@gmail.com>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Alex Williamson <alex.williamson@redhat.com>,
Yijing Wang <wangyijing@huawei.com>,
Paul Bolle <pebolle@tiscali.nl>
Cc: Rajat Jain <rajatjain@juniper.net>,
Rajat Jain <rajatxjain@gmail.com>,
Rajat Jain <rajatjain.linux@gmail.com>,
Guenter Roeck <groeck@juniper.net>,
Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH v2 0/4] Allow Link state changes for Hot-Plug
Date: Tue, 03 Dec 2013 14:31:52 -0800 [thread overview]
Message-ID: <529E5BD8.5090709@gmail.com> (raw)
Hello,
I had sent out this patchset as an "RFC" a few weeks back. It was briefly
discussed last week ( http://marc.info/?t=138513966800006&r=1&w=2 ). I was
wondering if you got a chance to look at this, and would appreciate it a
lot if this could be reviewed for inclusion in the tree.
In v2, I have dropped the use of module parameter as suggested by Bjorn.
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.
(As a side effect, this patch also fixes the bug
https://bugzilla.kernel.org/show_bug.cgi?id=65521 )
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 change notifications for hot-plug and removal
pciehp: Ensure very fast hotplug events are also processed.
pciehp: Introduce hotplug_lock to serialize HP events
drivers/pci/hotplug/pciehp.h | 5 ++
drivers/pci/hotplug/pciehp_core.c | 7 +-
drivers/pci/hotplug/pciehp_ctrl.c | 179 ++++++++++++++++++++++++++++++++-----
drivers/pci/hotplug/pciehp_hpc.c | 63 +++++++------
4 files changed, 200 insertions(+), 54 deletions(-)
--
1.7.9.5
reply other threads:[~2013-12-03 22:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=529E5BD8.5090709@gmail.com \
--to=rajatjain.linux@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=groeck@juniper.net \
--cc=kaneshige.kenji@jp.fujitsu.com \
--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=rajatxjain@gmail.com \
--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 NNTP newsgroup(s).