From: Borislav Petkov <bp@alien8.de>
To: David VomLehn <David.VomLehn@spacex.com>
Cc: linux-edac@vger.kernel.org, linux-rt-users@vger.kernel.org,
Robert Richter <rric@kernel.org>, Tony Luck <tony.luck@intel.com>
Subject: Re: EDAC messages about corrected errors affect realtime response
Date: Tue, 30 Apr 2013 11:05:20 +0200 [thread overview]
Message-ID: <20130430090520.GA12095@pd.tnic> (raw)
In-Reply-To: <20130430010733.GA1404@dvomlehn-z8.spacex.com>
On Mon, Apr 29, 2013 at 06:07:58PM -0700, David VomLehn wrote:
> Things I'd like feedback on:
> 1. Is sysfs even a reasonable place for this?
> 2. Is this a workable interface for this information? Note that, unlike
> the console, this is a lossy reporting mechanism.
> 3. Other suggestions?
Actually, the rough idea is to go a couple steps further and carry
RAS-related events using the perf infrastructure. A userspace daemon
then uses perf tool code to open a tracepoint in userspace and do
whatever it wants with that info. When this is done, you won't need
printk and the sysfs part of edac anymore - edac will only do mainly
DRAM ECC to DIMM decoding.
Robert and I are working on this currently and gladly welcome any help.
Here are some more concrete examples of what we want to do/what we're
working on:
http://lwn.net/Articles/425990/
http://thread.gmane.org/gmane.linux.kernel/1457591
HTH.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2013-04-30 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 1:07 EDAC messages about corrected errors affect realtime response David VomLehn
2013-04-30 9:05 ` 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=20130430090520.GA12095@pd.tnic \
--to=bp@alien8.de \
--cc=David.VomLehn@spacex.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rric@kernel.org \
--cc=tony.luck@intel.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).