From: Jin Dongming <jin.dongming@np.css.fujitsu.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Huang Ying <ying.huang@intel.com>, Ingo Molnar <mingo@elte.hu>,
"H.Peter Anvin" <hpa@zytor.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] [x86, next] Add mce_sys_info interface for debug.
Date: Mon, 01 Nov 2010 09:07:35 +0900 [thread overview]
Message-ID: <4CCE04C7.3050803@np.css.fujitsu.com> (raw)
In-Reply-To: <20101029081003.GB11149@basil.fritz.box>
Hi, Andi
Thanks for your review.
I will cancel this patch.
But I suggested there is such kind of tool for mce test.
It really costs too much time to confirm them one by one.
Best Regards,
Jin Dongming
(2010/10/29 17:10), Andi Kleen wrote:
> On Fri, Oct 29, 2010 at 01:42:23PM +0900, Jin Dongming wrote:
>> Add mce_sys_info interface for testing mce.
>>
>> Following is the reason why the interface is needed:
>> 1. Sometimes before testing mce, we want to know the basic
>> information of mce on the test machine. Though there are
>> some provided interfaces, there are some kernel variables
>> which could not be known still.
>
> That doesn't make sense to me. AFAIK everything is either available
> in sysfs or printed in the kernel log or can be known by knowing
> the hardware.
>
>> 2. When we inject mce data to test mce, the value of some
>> interfaces may be changed. It is hard for everybody to confirm
>> all the information of mce on the system.
>>
>> This interface could help us know what has happened and make mce test
>> become easier.
>
>
> The new interface seems overkill to me.
>
>>
>> The content of mce_sys_info will be like following:
>>
>> MCE status: Original/(Current) Value
>> mce_disabled: N
>
> Well you should know if you set that. It's also visible
> in the kernel log.
>
>>
>> mce_ser: 0/1
>
> That should be known or can be read directly.
>
>> tolerant: 1/1
>> panic_on_oops: 0/0
>> monarch_timeout: 1000000/1000000 us
>> mce_ignore_ce: 0/0
>> mce_cmci_disabled: N/N
>
> These are all in sysfs or in the command line.
>
>
>
>>
>> MCG Register:
>> CAP_Reg_Val BANKS EXT_CNT FUNCTIONS
>> 0x0000000000000806 0x06 0x00 TES
>
> You can just read that from /dev/cpu/*/msr if you really want it.
> No need to bloat the kernel.
>
> -Andi
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2010-11-01 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 4:42 Jin Dongming
2010-10-29 7:24 ` Borislav Petkov
2010-11-01 0:11 ` Jin Dongming
2010-10-29 8:10 ` Andi Kleen
2010-11-01 0:07 ` Jin Dongming [this message]
2010-11-01 14:00 ` Andi Kleen
2010-11-01 23:56 ` Jin Dongming
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=4CCE04C7.3050803@np.css.fujitsu.com \
--to=jin.dongming@np.css.fujitsu.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=ying.huang@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
Powered by JetHome