From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@linux.intel.com>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
tglx@linutronix.de, Yinghai Lu <yinghai@kernel.org>,
Huang Ying <ying.huang@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-tip-commits@vger.kernel.org
Subject: Re: [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit
Date: Mon, 17 Aug 2009 13:00:35 +0200 [thread overview]
Message-ID: <20090817110035.GA13972@elte.hu> (raw)
In-Reply-To: <4A893746.4040402@linux.intel.com>
* Andi Kleen <ak@linux.intel.com> wrote:
> Hidetoshi Seto wrote:
>
>> One possibility is: if the BIOS doesn't clear status in banks,
>> new mce codes will try to log such junks.
>>
>> If the junk is totally junk but can be decoded as a valid log
>> with MISCV or ADDRV bit, and if the cpu try to access register
>> which is not implemented (e.g. IA32_MCi_MISC/ADDR), then such
>> access might cause a general protection exception. (ref. ASDM 3A
>> 15.3.2.3)
>
> The MCA declares if it comes with ADDR or MISC in a status bit and
> the MCA code only accesses these MSRs if these status bits are
> set. Also I believe P3 implemented ADDR at least, likely even
> MISC.
>
> The old 32bit MCA code did that too
That's true, but did you also want to make a specific point?
Ingo
next prev parent reply other threads:[~2009-08-17 11:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-4efc0670baf4b14bc95502e54a83ccf639146125@git.kernel.org>
2009-08-12 11:36 ` [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit Ingo Molnar
2009-08-17 5:00 ` Hidetoshi Seto
2009-08-17 8:35 ` Ingo Molnar
2009-08-17 9:08 ` Hidetoshi Seto
2009-08-17 9:18 ` Ingo Molnar
2009-08-17 9:20 ` Ingo Molnar
2009-08-17 11:08 ` Andi Kleen
2009-08-17 11:24 ` Ingo Molnar
2009-09-22 15:41 ` Ingo Molnar
2009-09-23 15:22 ` Andi Kleen
2009-09-23 16:18 ` Ingo Molnar
2009-08-17 10:56 ` Andi Kleen
2009-08-17 11:00 ` Ingo Molnar [this message]
2009-08-17 11:29 ` [PATCH] x86, mce: Don't initialize MCEs on unknown CPUs Ingo Molnar
2009-08-17 11:35 ` Andi Kleen
2009-08-17 11:53 ` Ingo Molnar
2009-08-17 13:28 ` Andi Kleen
2009-08-17 11:25 ` [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit 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=20090817110035.GA13972@elte.hu \
--to=mingo@elte.hu \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@sisk.pl \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.com \
--cc=yinghai@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 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.