From: Borislav Petkov <bp@alien8.de>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: kyle-meyer <kyle.meyer@hpe.com>,
dimitri.sivanich@hpe.com, steve.wahl@hpe.com, tglx@linutronix.de,
mingo@redhat.com, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, tony.luck@intel.com, qiuxu.zhuo@intel.com,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH] RAS/CEC: Move non-debug attributes out of debugfs
Date: Tue, 28 Mar 2023 00:07:05 +0200 [thread overview]
Message-ID: <20230327220705.GFZCITiXbkfun7oh21@fat_crate.local> (raw)
In-Reply-To: <ZB4NFzrf09D1J47m@yaz-khff.amd.com>
On Fri, Mar 24, 2023 at 04:50:31PM -0400, Yazen Ghannam wrote:
> How about "/sys/ras" to collect global RAS interfaces?
Looking a bit at
Documentation/admin-guide/sysfs-rules.rst
it does sound like /sys/<subsystem> could be a good place. Might wanna
run it by Greg, though, first.
> Maybe it can link to other directories like "/sys/devices/*" for
> hardware things like MCA,
Those are at
/sys/devices/system/machinecheck/
> and "/sys/kernel/*" for kernel things like CEC.
Or /sys/drivers
Remember there's also
/sys/devices/system/edac/
so a lot of RAS junk spread all over the place.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2023-03-27 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 20:22 [PATCH] RAS/CEC: Move non-debug attributes out of debugfs kyle-meyer
2023-03-23 20:29 ` Dave Hansen
2023-03-23 21:52 ` Meyer, Kyle
2023-03-23 22:01 ` Dave Hansen
2023-03-24 0:49 ` Borislav Petkov
2023-03-24 20:50 ` Yazen Ghannam
2023-03-27 22:07 ` Borislav Petkov [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=20230327220705.GFZCITiXbkfun7oh21@fat_crate.local \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dimitri.sivanich@hpe.com \
--cc=hpa@zytor.com \
--cc=kyle.meyer@hpe.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qiuxu.zhuo@intel.com \
--cc=steve.wahl@hpe.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.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).