From: Thomas Gleixner <tglx@linutronix.de>
To: Chen Gong <gong.chen@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
Borislav Petkov <borislav.petkov@amd.com>,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [patch 0/5] x86: mce: Bugfixes, cleanups and a new CMCI poll version
Date: Fri, 8 Jun 2012 09:49:35 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1206080940360.3086@ionos> (raw)
In-Reply-To: <4FD07D8F.5020303@linux.intel.com>
On Thu, 7 Jun 2012, Chen Gong wrote:
>
> But during the CPU online/offline test I found an issue. After *STORM*
> mode is entered, it can't come back from *STORM* mode to normal
> interrupt mode. At least there exists such an issue: when *STORM* is
> entered, in the meanwhile, one CPU is offline during this period,
> which means *cmci_storm_on_cpus* can't decrease to 0 because there
> is one bit stuck on this offlined CPU. So we should detect such
> situation and decrease on *cmci_storm_on_cpus* at proper time.
Yes, we need to reset the storm state as well I think.
> BTW, even I online the *CPU* in above situation, the normal CMCI
> still doesn't come back, strange.
That's weird.
> I still have another question: When we handle following case:
> mce_cpu_callback(struct notifier_block *
> mce_device_remove(cpu);
> break;
> case CPU_DOWN_PREPARE:
> - del_timer_sync(t);
> smp_call_function_single(cpu, mce_disable_cpu, &action, 1);
> + del_timer_sync(t);
> break;
>
> Where we add this timer back? I can't find it in "case CPU_ONLINE".
The timer gets added back via mcheck_cpu_init(), which is called on
the newly onlined cpu from smp_callin().
Thanks,
tglx
next prev parent reply other threads:[~2012-06-08 7:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 21:53 [patch 0/5] x86: mce: Bugfixes, cleanups and a new CMCI poll version Thomas Gleixner
2012-06-06 21:53 ` [patch 1/5] x86: mce: Disable preemption when calling raise_local() Thomas Gleixner
2012-06-06 21:53 ` [patch 2/5] x86: mce: Serialize mce injection Thomas Gleixner
2012-06-06 21:53 ` [patch 3/5] x86: mce: Split timer init Thomas Gleixner
2012-06-07 15:18 ` Borislav Petkov
2012-06-20 3:35 ` Hidetoshi Seto
2012-06-06 21:53 ` [patch 4/5] x86: mce: Remove the frozen cases in the hotplug code Thomas Gleixner
2012-06-07 17:49 ` Borislav Petkov
2012-06-06 21:53 ` [patch 5/5] x86: mce: Add cmci poll mode Thomas Gleixner
2012-06-07 18:14 ` Borislav Petkov
2012-06-07 10:08 ` [patch 0/5] x86: mce: Bugfixes, cleanups and a new CMCI poll version Chen Gong
2012-06-07 13:35 ` Borislav Petkov
2012-06-07 16:22 ` Luck, Tony
2012-06-08 7:49 ` Thomas Gleixner [this message]
2012-06-11 5:46 ` Chen Gong
2012-06-11 6:09 ` Chen Gong
2012-06-14 13:49 ` [PATCH] tmp patch to fix hotplug issue in CMCI storm Chen Gong
2012-06-14 14:07 ` Thomas Gleixner
2012-06-15 6:51 ` Chen Gong
2012-06-15 9:55 ` Thomas Gleixner
2012-06-18 6:42 ` Chen Gong
2012-06-18 6:45 ` [PATCH V2] " Chen Gong
2012-06-18 8:00 ` Thomas Gleixner
2012-06-18 10:13 ` Chen Gong
2012-06-18 12:23 ` Thomas Gleixner
2012-06-19 6:05 ` Chen Gong
2012-06-19 6:09 ` [PATCH V3] " Chen Gong
2012-07-04 8:12 ` Chen Gong
2012-07-16 3:16 ` Chen Gong
2012-07-16 8:22 ` Thomas Gleixner
2012-07-17 21:47 ` Chen Gong
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=alpine.LFD.2.02.1206080940360.3086@ionos \
--to=tglx@linutronix.de \
--cc=borislav.petkov@amd.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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