From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
"ananth@in.ibm.com" <ananth@in.ibm.com>,
"masbock@linux.vnet.ibm.com" <masbock@linux.vnet.ibm.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bp@amd64.org" <bp@amd64.org>, "lcm@us.ibm.com" <lcm@us.ibm.com>,
"andi@firstfloor.org" <andi@firstfloor.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"gregkh@suse.de" <gregkh@suse.de>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH v3] x86/mce: Honour bios-set CMCI threshold
Date: Thu, 18 Oct 2012 11:13:14 +0530 [thread overview]
Message-ID: <507F96F2.9050305@linux.vnet.ibm.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F19D517FF@ORSMSX108.amr.corp.intel.com>
On 10/17/2012 10:58 PM, Luck, Tony wrote:
> BUT (squared) do you even really need to know that thresholds were set? You
> could look at bits {52:38} in the MCi_STATUS information for the bank to see
> how many corrected errors had been logged.
Ah, nice. I think we should be able to use this instead of the sysfs
attribute.
Thanks,
Naveen
next prev parent reply other threads:[~2012-10-18 5:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 5:31 [PATCH v2] x86/mce: Honour bios-set CMCI threshold Naveen N. Rao
2012-09-11 16:04 ` Tony Luck
2012-09-12 12:25 ` [PATCH v3] " Naveen N. Rao
2012-09-21 11:39 ` Naveen N. Rao
2012-10-17 10:59 ` Borislav Petkov
2012-10-17 11:27 ` Naveen N. Rao
2012-10-17 13:09 ` Borislav Petkov
2012-10-17 15:47 ` Naveen N. Rao
2012-10-17 16:40 ` Borislav Petkov
2012-10-17 17:28 ` Luck, Tony
2012-10-17 18:09 ` Borislav Petkov
2012-10-18 5:43 ` Naveen N. Rao [this message]
2012-10-18 13:24 ` Borislav Petkov
2012-10-18 16:46 ` Luck, Tony
2012-10-19 15:52 ` [tip:x86/urgent] x86, MCE: Remove bios_cmci_threshold sysfs attribute tip-bot for Borislav Petkov
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=507F96F2.9050305@linux.vnet.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=ananth@in.ibm.com \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=bp@amd64.org \
--cc=gong.chen@linux.intel.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=lcm@us.ibm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masbock@linux.vnet.ibm.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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).