On Thu, 2006-03-09 at 17:46 -0800, Dave Peterson wrote:
> > > Issue #3
> > > --------
> > > I am unclear about what to do here. If the list contents were
> > > read-only, it would be relatively easy to make
> > > /sys/devices/system/edac/pci/pci_parity_whitelist into a directory
> > > containing symlinks, one for each device. However, the user is
> > > supposed to be able to modify the list contents. This would imply
> > > that the user creates and destroys symlinks. Does sysfs currently
> > > support this sort of behavior? If not, what is the preferred
> > > means for implementing a user-modifiable set of values?
> > No it doesn't. How big can this list get?
> It depends on how many PCI devices in your machine you wish to
> blacklist or whitelist. The motivation for this feature is that
> certain known badly-designed devices report an endless stream of
> spurious PCI bus parity errors. We want to skip such devices when
> checking for PCI bus parity errors.
ok so this is actually a per pci device property!
I would suggest moving this property to the pci device itself, not doing
it inside an edac directory.
by doing that you get the advantage that 1) it's a more logical place,
and 2) users can do it even for 1 of 2 cards, if they have 2 cards of
the same make and 3) you can use the generic kernel quirk interface for
this and 4) drivers can in principle control this for their hardware in
I understand that on a PC, EDAC is the only user. but ppc has a similar
mechanism I suspect, and they more than likely would be able to share
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]