From: Keith Busch <keith.busch@intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Sathya Prakash <Sathya.Prakash@broadcom.com>,
linux-pci@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [Patch v1 0/7] mpt3sas: Hot-Plug Surprise removal support on IOC.
Date: Wed, 5 Sep 2018 08:17:13 -0600 [thread overview]
Message-ID: <20180905141712.GA19005@localhost.localdomain> (raw)
In-Reply-To: <20180905073816.jcrct2xcpucb6bkn@wunner.de>
On Wed, Sep 05, 2018 at 09:38:16AM +0200, Lukas Wunner wrote:
> On Wed, Sep 05, 2018 at 11:45:45AM +0530, Sreekanth Reddy wrote:
> > On Tue, Sep 4, 2018 at 3:12 PM, Lukas Wunner <lukas@wunner.de> wrote:
> > > Many scsi drivers call pci_channel_offline() to detect inaccessibility
> > > of the device due to a PCI error:
> > > https://elixir.bootlin.com/linux/v4.19-rc2/ident/pci_channel_offline
> > >
> > > A patch is pending such that surprise removal can also be queried
> > > with that same function:
> > > https://www.spinics.net/lists/linux-pci/msg75722.html
> >
> > Lukas, thanks for pointing to this pci_dev_is_disconnected() API. So
> > we can use this API directly instead of reading the vendor Id and
> > checking for all one's once this patch get accepted?
>
> Yes, except pci_dev_is_disconnected() is private to the PCI core,
> but dev->error_state and pci_channel_offline() is public.
The exported function to call is pci_device_is_present().
next prev parent reply other threads:[~2018-09-05 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1535690081-16116-1-git-send-email-suganath-prabu.subramani@broadcom.com>
[not found] ` <CAHp75VfC8GN3oEzSFJYfMr0iqBTYUJ=WPoLS9Oh5NgVcFmnBkw@mail.gmail.com>
2018-08-31 8:55 ` [Patch v1 0/7] mpt3sas: Hot-Plug Surprise removal support on IOC Lukas Wunner
2018-09-04 5:49 ` Sreekanth Reddy
2018-09-04 9:42 ` Lukas Wunner
2018-09-05 6:15 ` Sreekanth Reddy
2018-09-05 7:38 ` Lukas Wunner
2018-09-05 14:17 ` Keith Busch [this message]
2018-09-12 10:01 ` Sreekanth Reddy
2018-09-13 10:10 ` Lukas Wunner
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=20180905141712.GA19005@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=Sathya.Prakash@broadcom.com \
--cc=andy.shevchenko@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.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 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.