From: Andi Kleen <andi@firstfloor.org>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, hpa@zytor.com,
tglx@linutronix.de
Subject: Re: [PATCH] x86: mce: Xeon75xx specific interface to get corrected memory error information v2
Date: Mon, 29 Mar 2010 12:55:14 +0200 [thread overview]
Message-ID: <87fx3j75yl.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4BB0851B.3000908@jp.fujitsu.com> (Hidetoshi Seto's message of "Mon, 29 Mar 2010 19:46:51 +0900")
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> writes:
> I have some questions: Is it impossible to get the address
> after polling handler have processed? e.g. Is it possible to
> implement this module as mcelog's add-on that hooked & invoked
> immediately after reading /dev/mcelog? I guess there are
> some limitation/restriction to call pfa_command().
You need to be in ring 0. In theory you could do it later, but then
you risk losing the address if there is another error.
> Are there any alternative way to get the address?
No.
> Polling like edac_i7 doesn't help this?
No.
>
> You pointed "This makes it impossible to do predictive failure
> analysis", but I guess we could do rough-but-enough analysis that
> requires coarse resolution like sockets. Or we should not expect
The main predictive failure analysis interesting here is bad page
offlining and for that you need an address.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-03-29 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 5:40 [PATCH] x86: mce: Xeon75xx specific interface to get corrected memory error information v2 Andi Kleen
2010-03-29 7:47 ` Andi Kleen
2010-03-29 8:29 ` Hidetoshi Seto
2010-03-29 9:01 ` Andi Kleen
2010-03-29 10:46 ` Hidetoshi Seto
2010-03-29 10:55 ` Andi Kleen [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=87fx3j75yl.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.