From: Greg KH <greg@kroah.com>
To: Doug Thompson <norsk5@yahoo.com>
Cc: linux-kernel@vger.kernel.org, arjan@infradead.org,
bluesmoke-devel@lists.sourceforge.net
Subject: Re: [PATCH] PCI Bus Parity Status-broken hardware attribute, EDAC foundation
Date: Tue, 9 May 2006 15:58:55 -0700 [thread overview]
Message-ID: <20060509225855.GA14075@kroah.com> (raw)
In-Reply-To: <20060509000609.62160.qmail@web50101.mail.yahoo.com>
On Mon, May 08, 2006 at 05:06:09PM -0700, Doug Thompson wrote:
>
> PATCH against the 2.6.17-rc3 release.
>
> Currently, the EDAC (error detection and correction) modules that are in the kernel
> contain some features that need to be moved. After some good feedback on the PCI
> Parity detection code and interface
> (http://www.ussg.iu.edu/hypermail/linux/kernel/0603.1/0897.html) this patch ADDs an
> new attribute to the pci_dev structure: Namely the 'broken_parity_status' bit.
>
> When set this indicates that the respective hardware generates false positives of
> Parity errors.
>
> The EDAC "blacklist" solution was inferior and will be removed in a future patch.
>
> Also in this patch is a PCI quirk.c entry for an Infiniband PCI-X card which
> generates false positive parity errors.
>
> I am requesting comments on this AND on the possibility of a exposing this
> 'broken_parity_status' bit to userland via the PCI device sysfs directory for
> devices. This access would allow for enabling of this feature on new devices and for
> old devices that have their drivers updated. (SLES 9 SP3 did this on an ATI
> motherboard video device). There is a need to update such a PCI attribute between
> kernel releases.
>
> This patch just adds a storage place for the attribute and a quirk entry for a known
> bad PCI device. PCI Parity reaper/harvestor operations are in EDAC itself and will
> be refactored to use this PCI attribute instead of its own mechanisms (which are
> currently disabled) in the future.
I have no objection to this patch and have added it to my tree. If you
wish to export this information through sysfs, that's also ok. Feel
free to send a follow-on patch that does that.
thanks,
greg k-h
prev parent reply other threads:[~2006-05-09 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 0:06 [PATCH] PCI Bus Parity Status-broken hardware attribute, EDAC foundation Doug Thompson
2006-05-09 22:58 ` Greg KH [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=20060509225855.GA14075@kroah.com \
--to=greg@kroah.com \
--cc=arjan@infradead.org \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=norsk5@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.