[RFC/PATCH] How to block pci config-reads during device self-test?

Benjamin Herrenschmidt benh at kernel.crashing.org
Thu Jul 29 09:27:19 EST 2004


On Wed, 2004-07-14 at 09:03, Linas Vepstas wrote:
>
> On Thu, Jul 08, 2004 at 11:36:28AM -0500, Brian King was heard to remark:
> > I've been doing some talking with various hardware folks to see if
> > there is a way to get this fixed and so far the answer I have been
> > getting is no. It is how the hardware works and there isn't much
> > that can be done about it ...
>
> Actually, the hardware isn't broken ... its working as designed, more
> or less per pci spec. See below for techninical details.

Catching up a bit late... the whole in_interrupt() test with semaphore
is totally disgusting... Also, PCI ops are called within a spinlock
anyway.

Just make it fail (return FF's)

--
Benjamin Herrenschmidt <benh at kernel.crashing.org>

** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/





More information about the Linuxppc64-dev mailing list