LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org> To: Keith Busch <keith.busch@intel.com> Cc: Sinan Kaya <okaya@codeaurora.org>, Oza Pawandeep <poza@codeaurora.org>, Bjorn Helgaas <bhelgaas@google.com>, Philippe Ombredanne <pombredanne@nexb.com>, Thomas Gleixner <tglx@linutronix.de>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Kate Stewart <kstewart@linuxfoundation.org>, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Dongdong Liu <liudongdong3@huawei.com>, Wei Zhang <wzhang@fb.com>, Timur Tabi <timur@codeaurora.org>, Alex Williamson <alex.williamson@redhat.com> Subject: Re: [PATCH v12 0/6] Address error and recovery for AER and DPC Date: Tue, 8 May 2018 14:25:32 -0500 [thread overview] Message-ID: <20180508192532.GA79697@bhelgaas-glaptop.roam.corp.google.com> (raw) In-Reply-To: <20180312232626.GI18494@localhost.localdomain> On Mon, Mar 12, 2018 at 05:26:26PM -0600, Keith Busch wrote: > On Mon, Mar 12, 2018 at 02:47:30PM -0500, Bjorn Helgaas wrote: > > On Mon, Mar 12, 2018 at 08:25:51AM -0600, Keith Busch wrote: > > > Per spec, DPC is the recommended way for handling surprise removal > > > events and even recommends DPC capable slots *not* set 'Surprise' > > > in Slot Capabilities so that removals are always handled by DPC. This > > > service driver was developed with that use in mind. > > > > Thanks for this tip. The only thing I've found so far is the mention > > of Surprise Down triggering DPC in the last paragraph of sec 6.7.5. > > Are there other references I should look at? I haven't found the > > recommendation about not setting 'Surprise' in Slot Capabilities yet. > > No problem, it's in the "IMPLEMENTATION NOTE" at the end of 6.2.10.4, > "Avoid Disabled Link and Hot-Plug Surprise Use with DPC". > > Outside the spec, Microsemi as one of the PCI-SIG contributors and early > adopters of the capability published a white paper "Hot and Surprise > Plug Recommendations for Enterprise PCIe" providing guidance for OS > drivers using DPC. We originally developed to that guidance. The paper > unfortunately appears to be pay-walled now. :( Any chance you have a URL or contact info for this pay-walled white paper? Sounds like it might have useful information in it.
next prev parent reply other threads:[~2018-05-08 19:25 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-28 17:04 [PATCH v12 0/6] Address error and recovery for AER and DPC Oza Pawandeep 2018-02-28 17:04 ` [PATCH v12 1/6] PCI/AER: Rename error recovery to generic PCI naming Oza Pawandeep 2018-02-28 17:04 ` [PATCH v12 2/6] PCI/AER: Factor out error reporting from AER Oza Pawandeep 2018-02-28 17:04 ` [PATCH v12 3/6] PCI/PORTDRV: Implement generic find service Oza Pawandeep 2018-03-06 14:02 ` Sinan Kaya 2018-03-08 7:56 ` poza 2018-02-28 17:04 ` [PATCH v12 4/6] PCI/DPC: Unify and plumb error handling into DPC Oza Pawandeep 2018-02-28 17:04 ` [PATCH v12 5/6] PCI: Unify wait for link active into generic PCI Oza Pawandeep 2018-02-28 17:04 ` [PATCH v12 6/6] PCI/DPC: Enumerate the devices after DPC trigger event Oza Pawandeep 2018-03-11 22:03 ` [PATCH v12 0/6] Address error and recovery for AER and DPC Bjorn Helgaas 2018-03-12 3:03 ` Sinan Kaya 2018-03-12 14:25 ` Keith Busch 2018-03-12 14:46 ` poza 2018-03-12 14:58 ` Keith Busch 2018-03-12 15:34 ` poza 2018-03-12 17:33 ` Keith Busch 2018-03-12 17:41 ` Sinan Kaya 2018-03-12 17:56 ` Keith Busch 2018-03-12 19:47 ` Bjorn Helgaas 2018-03-12 23:26 ` Keith Busch 2018-03-13 3:47 ` Sinan Kaya 2018-03-14 20:50 ` Keith Busch 2018-03-14 21:00 ` Sinan Kaya 2018-05-08 19:25 ` Bjorn Helgaas [this message] 2018-03-12 14:01 ` poza
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=20180508192532.GA79697@bhelgaas-glaptop.roam.corp.google.com \ --to=helgaas@kernel.org \ --cc=alex.williamson@redhat.com \ --cc=bhelgaas@google.com \ --cc=gregkh@linuxfoundation.org \ --cc=keith.busch@intel.com \ --cc=kstewart@linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=liudongdong3@huawei.com \ --cc=okaya@codeaurora.org \ --cc=pombredanne@nexb.com \ --cc=poza@codeaurora.org \ --cc=tglx@linutronix.de \ --cc=timur@codeaurora.org \ --cc=wzhang@fb.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: linkBe 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).