All of lore.kernel.org
 help / color / mirror / Atom feed
From: nilesh.tayade@netscout.com (Nilesh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Query about a PCI device error detection.
Date: Wed, 13 Jul 2011 15:11:57 +0530	[thread overview]
Message-ID: <4E1D6865.60908@netscout.com> (raw)
In-Reply-To: <1309948015.26383.33.camel@nilesh-desktop>

Resending the email to kernelnewbies list as well (have sent the same to 
edac mailing list). Appreciate any pointers on below query, if any one 
has worked on edac.

On Wednesday 06 July 2011 03:56 PM, nilesh wrote:
> Hi,
>
> I am fairly new to the edac driver and have some basic query regarding
> the error detection in case of PCI devices. I could see the module for
> memory controller's error detection is done s.t. UE/CE/controller
> specific errors are scanned and detected, also the PCI errors are also
> scanned.
>
> E.g. in case of i5400 :
> i5400_edac.c :
> i5400_probe1()
> {
>
> 1285         /* Set the function pointer to an actual operation function
> */
> 1286         mci->edac_check = i5400_check_error;
> ...
> 1312         /* allocating generic PCI control info */
> 1313         i5400_pci = edac_pci_create_generic_ctl(&pdev->dev,
> EDAC_MOD_STR);
> }
>
> And we check the PCI status registers for the errors.
> edac_pci_generic_check() -->  edac_pci_do_parity_check() -->
> edac_pci_dev_parity_test()
>
> So, i5400_check_error - detect UE/CE.
> edac_pci_generic_check - detect PCI errors.
>
> Query:
> ------
> * If one wants to get the errors harvested for non-MC device (e.g.
> ethernet controller etc.) is it going to be done through
> edac_pci_generic_check() automatically - as we already scan through all
> PCI devices in a loop? Is it required to add the separate module for
> that device?
>

-- 
Thanks,
Nilesh

           reply	other threads:[~2011-07-13  9:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1309948015.26383.33.camel@nilesh-desktop>]

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=4E1D6865.60908@netscout.com \
    --to=nilesh.tayade@netscout.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.