From: Hugh Dickins <hugh@veritas.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Andi Kleen <ak@suse.de>,
luming.yu@intel.com, racing.guo@intel.com, davej@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] x86 port lockless MCE quirky bank0
Date: Wed, 18 May 2005 13:34:25 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0505181302410.4517@goblin.wat.veritas.com> (raw)
In-Reply-To: <20050517153941.7d99d1f6.akpm@osdl.org>
On Tue, 17 May 2005, Andrew Morton wrote:
>
> Yes. I'll drop the following from -mm:
>
> x86-port-lockless-mce-preparation.patch
> x86-port-lockless-mce-implementation.patch
> x86-port-lockless-mce-implementation-fix.patch
> x86-port-lockless-mce-implementation-fix-2.patch
The right decision for now, I think - thanks.
I presume they may return later on, so I'd better confess:
I lied when I said my patch fixed the P6 bank0 issue, I was confused
between rebuildings and rebootings. It should have fixed the issue,
but the patch which actually fixed it was one earlier, which had an
off-by-one ("> quirky_bank0") which I'd corrected before posting.
The ">= quirky_bank0" patch was not enough to fix the issue because...
mce_cpu_quirks (and mce_init and mce_cpu_features) are never called at
startup (on Intel or Centaur), because the logic in machine_check_init
(see below) to call mcheck_init is broken.
Which explains why I got the freeze at resume not at startup,
and casts doubt on how much any of it has got tested so far.
Hugh
void __devinit machine_check_init(struct cpuinfo_x86 *c)
{
if (mce_dont_init)
return;
switch (c->x86_vendor) {
case X86_VENDOR_INTEL:
if (c->x86==5)
intel_p5_mcheck_init(c);
break;
case X86_VENDOR_CENTAUR:
if (c->x86==5)
winchip_mcheck_init(c);
break;
default:
machine_check_vector = do_machine_check;
wmb();
mcheck_init(c);
break;
}
}
prev parent reply other threads:[~2005-05-18 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 20:18 Hugh Dickins
2005-05-17 20:24 ` Andi Kleen
2005-05-17 22:39 ` Andrew Morton
2005-05-18 12:34 ` Hugh Dickins [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=Pine.LNX.4.61.0505181302410.4517@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=racing.guo@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
all inboxes | Powered by JetHome®