From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: Andi Kleen <andi@firstfloor.org>
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 17:29:52 +0900 [thread overview]
Message-ID: <4BB06500.5060105@jp.fujitsu.com> (raw)
In-Reply-To: <87vdcf7ent.fsf@basil.nowhere.org>
(2010/03/29 16:47), Andi Kleen wrote:
> Andi Kleen <andi@firstfloor.org> writes:
>
>> x86: mce: Xeon75xx specific interface to get corrected memory error information v2
>
> Ping? Please review this patch. Thanks.
> -Andi
>
>>
>> [This version addresses the previous comments. It does not change
>> any interface to the outside and does not attempt to encode DIMMs
>> or anything like that, but only passes out the physical address of u
>> a corrected error in the standard ADDR register field.
>> So for the outside it looks exactly the same as if the CPU supported this
>> natively, but no otherwise special interfaces.
>>
>> I hope this addresses previous concerns. I guess the DIMM error reporting
>> can be revisited once there's a new reporting interface. There are still
>> some traces of DIMM parsing in there, but it's only used for debug
>> purposes now.]
>>
>> ---
>>
>> Xeon 75xx doesn't log physical addresses on corrected machine check
>> events in the standard architectural MSRs. Instead the address has to
>> be retrieved in a model specific way. This makes it impossible
>> to do predictive failure analysis.
Could you point proper specification or datasheet to know/check what
you are going to do here?
Thanks,
H.Seto
next prev parent reply other threads:[~2010-03-29 8:30 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 [this message]
2010-03-29 9:01 ` Andi Kleen
2010-03-29 10:46 ` Hidetoshi Seto
2010-03-29 10:55 ` Andi Kleen
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=4BB06500.5060105@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox