creating PCI-related sysfs entries

Linas Vepstas linas at austin.ibm.com
Fri Feb 3 03:36:36 EST 2006


On Wed, Feb 01, 2006 at 10:52:43PM -0700, Grant Grundler was heard to remark:
> On Wed, Feb 01, 2006 at 03:35:46PM -0600, linas wrote:
> > > Sounds like you want to add another method for error recovery
> > > stats/control.
> > 
> > Actually, the "recovery" part is already (mostly) in mainline,
> > See Documentation/pci-error-recovery.txt
> 
> What I meant was, you want to formalize error recovery methods
> and make it a peer to the other resources access methods I listed.

Hmm. Not sure what you mean by "a peer". pci config-space i/o is done
through callbacks in the pci bus->ops structure. The PCI error recovery
is done via callbacks in the pci dev structure.  Was there something 
you'd like to see done differently?

Given GregKH's remarks, it sounded like there was some interest in 
a "struct bus_host_bridge" abstraction, and I'd be willing
to take a shot at that, provided there is general interest and 
general agreement.  I'm not quite sure what such a struct might 
contain, just yet, I'm just imagining it might be non-empty.

> "Nguyen, Tom L" <tom.l.nguyen at intel.com> has proposed patches
> to support PCI-e AER (Advanced Error Reporting):

I kept looking at AER, and could not figure out what to do 
with it. 

--linas



More information about the Linuxppc64-dev mailing list