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 11:47:06 +0300 [thread overview]
Message-ID: <50666803-ed9d-670a-e9a0-994547e4cdf8@amazon.com> (raw)
In-Reply-To: <20200511142619.GD25861@zn.tnic>
On 5/11/2020 5:26 PM, Borislav Petkov wrote:
> On Mon, May 11, 2020 at 05:21:14PM +0300, Hawa, Hanna wrote:
>> I'm trying to create different block names e.g. hw_block_a, hw_block_b.
>
> Please give an actual example of the names you're trying to add and how
> the hierarchy you think should look like.
For example PCIe controller interface, that can report on different
errors, e.g. axi read parity error, axi write parity error, completion
timeout, write overflow error, and parity error.
Then I think the hierarchy should look:
pcie/pcie0/..
/axi_write_parity_error/ce_count
/ue_count
/axi_read_parity_error/ce_count
/ue_count
/completion_timeout/ce_count
/ue_count
/write_overflow_error/ce_count
/ue_count
/parity_error/ce_count
/ue_count
same for pcie1/pcie2
Thanks,
Hanna
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
next prev parent reply other threads:[~2020-05-12 8:47 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 [this message]
2020-05-12 10:35 ` Borislav Petkov
2020-05-12 19:27 ` Hawa, Hanna
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=50666803-ed9d-670a-e9a0-994547e4cdf8@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