From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Allexio Ju <allexio.ju@gmail.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linas@austin.ibm.com,
yanmin.zhang@intel.com, linux-kernel@vger.kernel.org
Subject: Re: Questions on PCI express AER support in HBA driver
Date: Fri, 19 Jan 2007 10:30:49 +0800 [thread overview]
Message-ID: <1169173849.15989.273.camel@ymzhang> (raw)
In-Reply-To: <a02278b00701181246y51c04491k9d6d0be3c6c693a2@mail.gmail.com>
On Thu, 2007-01-18 at 12:46 -0800, Allexio Ju wrote:
> > What are the expected changes on SCSI LLD driver in regards to PCIE
> > AER supporting? I understood that the driver need to call following
> > APIs during probing to enable AER support for the device,
> > ---
> > if (pci_find_aer_capability(dev)) {
> > pci_enable_pcie_error_reporting(dev);
> > }
This is just to enable the error reporting of the device. One of the important
parts of AER is error recovery.
When an AER error happens, device will send an error message to root port. Then,
root port will notify kernel by interrupt. Kernel will print out error message,
and do error recovery to recover the related devices. Such recovery need device
drivers to provide a couple of callbacks. Documentation/pci-error-recovery.txt
has the detailed callback definitions and the recovery steps.
> > ---
> > What else does SCSI LLD driver need to changed?
Usually, 3 callbacks are enough while error_detected is must.
int (*error_detected)(struct pci_dev *dev, enum pci_channel_state);
int (*slot_reset)(struct pci_dev *dev);
void (*resume)(struct pci_dev *dev);
You could refer to the patches of e1000 drivers written by Linas, or just read
the source codes of the 3 callbacks of e1000 drivers in the latest kernel.
Yanmin
next prev parent reply other threads:[~2007-01-19 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 19:46 Allexio Ju
2007-01-18 20:46 ` Allexio Ju
2007-01-19 2:30 ` Zhang, Yanmin [this message]
2007-01-18 23:56 ` Linas Vepstas
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=1169173849.15989.273.camel@ymzhang \
--to=yanmin_zhang@linux.intel.com \
--cc=allexio.ju@gmail.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=yanmin.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®