From: Keith Busch <keith.busch@intel.com>
To: Austin.Bolen@dell.com
Cc: Alex_Gagniuc@Dellteam.com, linux-pci@vger.kernel.org,
bhelgaas@google.com, lukas@wunner.de
Subject: Re: PCI: hotplug: Erroneous removal of hotplug PCI devices
Date: Thu, 24 Jan 2019 13:20:20 -0700 [thread overview]
Message-ID: <20190124202020.GB9600@localhost.localdomain> (raw)
In-Reply-To: <b32e6ca62ae2494f98450df81ca1ee14@AUSX13MPC131.AMER.DELL.COM>
[in plain text for the mailing lists]
On Thu, Jan 24, 2019 at 08:10:47PM +0000, Austin.Bolen@dell.com wrote:
> On 1/23/2019 12:46 PM, Keith Busch wrote:
>
> On Wed, Jan 23, 2019 at 06:20:57PM +0000, Alex_Gagniuc@Dellteam.com<mailto:Alex_Gagniuc@Dellteam.com> wrote:
>
>
> <snip>
>
> Solution 1 is to say it's a spec violation, so ignore it. They'll change
> the "logical OR" thing in the next PCIe spec, so we still will have to
> worry about this.
>
>
>
> When's that changing? 5.0 is the next spec, and it still says:
>
> Presence Detect State - This bit indicates the presence of an adapter
> in the slot, reflected by the logical "OR" of the Physical Layer
> in-band presence detect mechanism and, if present, any out-of-band
> presence detect mechanism defined for the slot's corresponding
> form factor.
>
>
> The ECN that changes this behavior (Async Hot-Plug Updates ECN) is
> ratified and published to the PCI-SIG website. It modifies PCIe Base
> Spec 4.0 and will be incorporated into PCIe Base Spec 5.0. Check out
> the ECN section titled "In-band Presence Detect Mechanism Deprecated
> for Async Hot-Plug".
My copy of the 5.0-0.9 spec missed out on this ECN. The new changes look
like it more clearly defines expected software and hardware behavior,
so I'm looking forward to seeing the hardware implementations. Thanks
for driving that.
next prev parent reply other threads:[~2019-01-24 20:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 18:20 PCI: hotplug: Erroneous removal of hotplug PCI devices Alex_Gagniuc
2019-01-23 18:44 ` Keith Busch
2019-01-23 19:02 ` Lukas Wunner
2019-01-23 19:07 ` Keith Busch
2019-01-23 19:15 ` Lukas Wunner
2019-01-23 19:33 ` Keith Busch
2019-01-24 22:43 ` Austin.Bolen
2019-01-24 22:52 ` Austin.Bolen
[not found] ` <b32e6ca62ae2494f98450df81ca1ee14@AUSX13MPC131.AMER.DELL.COM>
2019-01-24 20:20 ` Keith Busch [this message]
2019-01-24 22:00 ` Austin.Bolen
2019-01-25 8:22 ` Lukas Wunner
2019-01-25 22:39 ` Austin.Bolen
2019-01-26 12:12 ` Lukas Wunner
2019-01-30 14:28 ` Austin.Bolen
2019-01-23 18:54 ` Lukas Wunner
2019-01-23 19:07 ` Lukas Wunner
2019-01-23 19:09 ` Keith Busch
2019-01-23 19:28 ` Lukas Wunner
2019-01-23 19:47 ` Keith Busch
2019-01-23 20:10 ` Alex_Gagniuc
2019-01-23 23:50 ` Alex_Gagniuc
2019-01-24 9:25 ` Lukas Wunner
2019-01-24 22:33 ` Austin.Bolen
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=20190124202020.GB9600@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=Alex_Gagniuc@Dellteam.com \
--cc=Austin.Bolen@dell.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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.