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: Mon, 11 May 2020 17:21:14 +0300 [thread overview]
Message-ID: <2fc308f9-47d6-7c75-775b-3f6579dfe571@amazon.com> (raw)
In-Reply-To: <20200511135507.GC25861@zn.tnic>
On 5/11/2020 4:55 PM, Borislav Petkov wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
>
>
> On Mon, May 11, 2020 at 03:59:38PM +0300, Hawa, Hanna wrote:
>> Can the edac device infrastructure support different block names? Shall we
>> add support for such feature?
>
> Does the "EDAC Blocks" section here:
>
> Documentation/driver-api/edac.rst
>
> answer your question?
Hi Boris,
Thanks for your quick answer, according to the section you point to, the
block names shall be different e.g. L1-cache/L2-cache. But when
initializing the sysfs block names, the block index appends the
block-name [1].
I'm trying to create different block names e.g. hw_block_a, hw_block_b.
[1]:
https://elixir.bootlin.com/linux/v5.7-rc5/source/drivers/edac/edac_device.c#L161
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
next prev parent reply other threads:[~2020-05-11 14:21 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 [this message]
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
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=2fc308f9-47d6-7c75-775b-3f6579dfe571@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).