From: Keith Busch <keith.busch@intel.com>
To: Rajat Jain <rajatja@google.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH] pciehp: Enable hot plug capable detection
Date: Fri, 4 Aug 2017 01:07:51 -0400 [thread overview]
Message-ID: <20170804050751.GA842@localhost.localdomain> (raw)
In-Reply-To: <20170804034631.GB478@localhost.localdomain>
On Thu, Aug 03, 2017 at 11:46:31PM -0400, Keith Busch wrote:
>
> Surprise removal is not supported. These do have Power Controller Control,
> though, and the user is supposed to power off the slot first like this:
>
> echo 0 > /sys/bus/pci/slot/<slot>/power
>
> Then they can manually remove the device safely. They don't always do
> that, though, and it seems surprise yanks happen to work, but I doubt
> that's 100% safe.
>
> Their expectation for hot add was that the kernel would handle it without
> the manual power control, and maybe that's not a valid expectation with
> this hardware even though it appears to work with my patch.
>
> After reading all this, I'm starting to reconsider my patch, as well as
> the users' current processes. Maybe they should be using sysfs in lieu
> of physical attention buttons. To make that work, I will request they
> disable pciehp polling and require the user initiate the hot add with
> the slot's sysf. I will check if this is acceptable and have them run
> tests to confirm if that works.
Didn't take long to get confirmation: orderly add/remove through sysfs is
successful and acceptable. It even has better results than the previous
pciehp polling behavior, which occasionally experienced link training
failures. Considering all the information now, this even feels like the
correct way to have done things from the start.
Unless I hear anything different, I would like to self-Nak the patch at
this time. Thank you all for taking the time to consider.
next prev parent reply other threads:[~2017-08-04 5:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 5:15 [PATCH] pciehp: Enable hot plug capable detection Keith Busch
2017-08-02 17:32 ` Bjorn Helgaas
2017-08-03 3:59 ` Keith Busch
2017-08-03 20:10 ` Bjorn Helgaas
2017-08-03 23:00 ` Rajat Jain
2017-08-04 3:46 ` Keith Busch
2017-08-04 5:07 ` Keith Busch [this message]
2017-08-04 1:58 ` Keith Busch
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=20170804050751.GA842@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rajatja@google.com \
--cc=yinghai@kernel.org \
/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).