From: Keith Busch <keith.busch@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 2/2] pci: Add ignore indicator quirk for devices
Date: Mon, 22 Aug 2016 17:15:36 -0400 [thread overview]
Message-ID: <20160822211536.GE28276@localhost.localdomain> (raw)
In-Reply-To: <20160822165524.GC18628@localhost>
On Mon, Aug 22, 2016 at 11:55:24AM -0500, Bjorn Helgaas wrote:
> I was imagining these LEDs as some sort of extension to the PCIe
> hotplug model, but I think that was a mistake: logically, they have
> nothing to do with hotplug, and the only reason they're currently
> associated with hotplug is because you chose to re-use a bus (VPP)
> that happens to be connected to the Slot Control registers.
>
> From an architectural point of view, these LEDs seem device-specific
> or storage-specific, with no connection to PCIe at all, so I don't
> know why we would put them in the PCIe spec or teach pciehp about
> them.
It's not entirely for hotplug scenarios, but it does help with user pain
points locating devices they intend to hot remove.
I hear many vendors are for the concept of proposing new status
and location indicator definitions to PCIe. I don't think anyone is
suggesting the implementation requiring this patch be made standard;
this generation of hardware is just a non-standard implementation that
needs a quirk to help fill the gap.
Would it be more palatable if I modify the quirk such that when set,
pciehp provides a sysfs entry allowing arbitrary user defined Slot Control
commands? That removes the dangerous direct access from user space.
next prev parent reply other threads:[~2016-08-22 21:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 20:19 [PATCH 1/2] pci: add option to ignore slot capabilities Keith Busch
2016-08-08 20:19 ` [PATCH 2/2] pci: Add ignore indicator quirk for devices Keith Busch
2016-08-15 17:40 ` Bjorn Helgaas
2016-08-15 19:23 ` Keith Busch
2016-08-15 19:50 ` Bjorn Helgaas
2016-08-15 22:35 ` Keith Busch
2016-08-16 3:03 ` Bjorn Helgaas
2016-08-17 21:37 ` Bjorn Helgaas
2016-08-17 23:09 ` Keith Busch
2016-08-18 19:56 ` Bjorn Helgaas
2016-08-18 22:46 ` Keith Busch
2016-08-22 16:55 ` Bjorn Helgaas
2016-08-22 21:15 ` Keith Busch [this message]
2016-08-23 13:39 ` Bjorn Helgaas
2016-08-23 17:10 ` Keith Busch
2016-08-23 17:14 ` Sinan Kaya
2016-08-23 19:23 ` Keith Busch
2016-08-23 19:52 ` Bjorn Helgaas
2016-08-23 20:44 ` Keith Busch
2016-08-23 20:02 ` Bjorn Helgaas
2016-08-24 17:33 ` Keith Busch
2016-08-13 0:03 ` [PATCH 1/2] pci: add option to ignore slot capabilities Sean O. Stalley
2016-08-13 0: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=20160822211536.GE28276@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.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).