From: "Hawa, Hanna" <hhhawa@amazon.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "james.morse@arm.com" <james.morse@arm.com>,
Robert Richter <rrichter@marvell.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"Krupnik, Ronen" <ronenk@amazon.com>, <talel@amazon.com>,
<jonnyc@amazon.com>, "Hanoch, Uri" <hanochu@amazon.com>
Subject: Re: [RFC] Support different block names with same EDAC device
Date: Tue, 12 May 2020 22:27:07 +0300 [thread overview]
Message-ID: <d4886b17-3d69-2cd0-2999-6eb10e3d5926@amazon.com> (raw)
In-Reply-To: <20200512103500.GA6859@zn.tnic>
On 5/12/2020 1:35 PM, Borislav Petkov wrote:
> The "...pci" layout on my box looks like this:
>
> $ tree/sys/devices/system/edac/pci/
> /sys/devices/system/edac/pci/
> ├── check_pci_errors
> ├── edac_pci_log_npe
> ├── edac_pci_log_pe
> ├── edac_pci_panic_on_pe
> ├── pci0
> │ ├── device -> ../../../../pci0000:00/0000:00:18.0
> │ ├── npe_count
> │ └── pe_count
> ├── pci_nonparity_count
> └── pci_parity_count
>
> so what's wrong with having "pcie0, pcie1, pcie2, ..." for those
> different functional units?
The pci layout on EDAC supports counters for parity/non parity errors.
We are searching for something more general. To add more error for PCIe
layout, to have counters, and to control panic flag per error.
>
> I guess you could add a "name" node so that you have:
>
> pcie
> |-> pcie0
> |-> name: axi_write_parity_error
> |-> ce_count
> |-> ue_count
>
> and so on so that tools can know what those FUs are.
Didn't get your suggestion, where can I add name?
Thanks,
Hanna
next prev parent reply other threads:[~2020-05-12 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 12:59 [RFC] Support different block names with same EDAC device Hawa, Hanna
2020-05-11 13:55 ` Borislav Petkov
2020-05-11 14:21 ` Hawa, Hanna
2020-05-11 14:26 ` Borislav Petkov
2020-05-12 8:47 ` Hawa, Hanna
2020-05-12 10:35 ` Borislav Petkov
2020-05-12 19:27 ` Hawa, Hanna [this message]
2020-05-12 20:01 ` Borislav Petkov
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=d4886b17-3d69-2cd0-2999-6eb10e3d5926@amazon.com \
--to=hhhawa@amazon.com \
--cc=bp@alien8.de \
--cc=dwmw@amazon.co.uk \
--cc=hanochu@amazon.com \
--cc=james.morse@arm.com \
--cc=jonnyc@amazon.com \
--cc=linux-edac@vger.kernel.org \
--cc=ronenk@amazon.com \
--cc=rrichter@marvell.com \
--cc=talel@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).