From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Andrew Patterson <andrew.patterson@hp.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH V4: 1/3] pci: Provide Multiple Error Received and no error source id support on AER
Date: Mon, 15 Jun 2009 09:48:15 +0800 [thread overview]
Message-ID: <1245030495.2560.344.camel@ymzhang> (raw)
In-Reply-To: <1244845057.19708.116.camel@grinch>
On Fri, 2009-06-12 at 22:17 +0000, Andrew Patterson wrote:
> On Fri, 2009-06-12 at 11:08 +0800, Zhang, Yanmin wrote:
> > Anyone could help me test it on powerpc? Or at least a compilation
> > to see there is any compiling error/warning. I have no powerpc machine.
> > Thanks.
> >
> > Changelog V4:
> > Port the patches to Jesses' linux-next tree (mostly based on
> > 2.6.30).
> >
> > Changelog V3:
> > 1) Probe devices under the root port when the bus id of
> > the source id is equal to 0; V2 does so when device id is
> > equal to 0;
> > 2) Add more comments on critical path of finding devices.
> >
> > Changelog V2:
> > Version 2 adds nosourceid, a boot parameter. When
> > aerdriver.nosourceid=y, aerdriver doesn't use the source
> > id saved by root port. Instead, it searches the device
> > tree under the root port to find the reporter. So if hardware
> > has errata and root port saves a bad source id, aerdriver
> > still could find the reporter.
> > There are 2 scenarios under which aerdriver searches the
> > device tree under root port:
> > 1) nosourceid=n and error source id is equal to 0;
> > 2) nosourceid=y.
> >
> > Based on PCI Express AER specs, a root port might receive multiple
> > TLP errors while it could only save a correctable error source id
> > and an uncorrectable error source id at the same time. In addition,
> > some root port hardware might be unable to provide a correct source
> > id, i.e., the source id, or the bus id part of the source id provided
> > by root port might be equal to 0.
> >
> > The patchset implements the support in kernel by searching the device
> > tree under the root port.
> >
> > Patch 1 changes parameter cb of function pci_walk_bus to return a value.
> > When cb return non-zero, pci_walk_bus stops more searching on the
> > device tree.
> >
> > Signed-off-by: Zhang Yanmin <yanmin.zhang@linux.intel.com>
> >
>
> This one looks fine to me.
>
> Reviewed-by: Andrew Patterson <andrew.patterson@hp.com>
Thanks for helping review the patches.
Yanmin
prev parent reply other threads:[~2009-06-15 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 3:08 [PATCH V4: 1/3] pci: Provide Multiple Error Received and no error source id support on AER Zhang, Yanmin
2009-06-12 22:17 ` Andrew Patterson
2009-06-15 1:48 ` Zhang, Yanmin [this message]
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=1245030495.2560.344.camel@ymzhang \
--to=yanmin_zhang@linux.intel.com \
--cc=andrew.patterson@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.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