From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: Chen Yucong <slaoub@gmail.com>
Cc: tony.luck@intel.com, bp@alien8.de, ak@linux.intel.com,
ying.huang@intel.com, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org
Subject: Re: [PATCH v2] x86/mce: Distirbute the clear operation of mces_seen to Per-CPU rather than only monarch CPU
Date: Wed, 21 May 2014 11:43:08 +0900 [thread overview]
Message-ID: <537C12BC.6080408@jp.fujitsu.com> (raw)
In-Reply-To: <1400637782.14703.32.camel@debian>
(2014/05/21 11:03), Chen Yucong wrote:
> On Wed, 2014-05-21 at 10:40 +0900, Hidetoshi Seto wrote:
>> (2014/05/20 11:11), Chen Yucong wrote:
>>> mces_seen is a Per-CPU variable which should only be accessed by Per-CPU as possible. So the
>>> clear operation of mces_seen should also be lcoal to Per-CPU rather than monarch CPU.
>>
>> I don't think it should be local.
>> Originally what we want to have here is memory to save mces_seen for each online cpus,
>> such as a global array like mces_seen[cpus]. But at same time we don't want to preallocate
>> big array enough for max possible cpus. So we use per-cpu store instead.
>>
> But mces_seen will just be updated by Per-CPU rather than monarch CPU.
> It is only read by monarch CPU.
Because mce status registers are per-cpu and monarch cannot access subjects' registers
directly, all subjects read it's status for monarch, store the status to memory for monarch,
and then monarch gather all status to make decision for all.
At last monarch kindly clear gathered status for all.
It will be one of important steps to ready for next mce events.
I think you should clarify why "distributing the clear operation" is required here.
What is the benefit?
Thanks,
H.Seto
next prev parent reply other threads:[~2014-05-21 2:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 2:11 [PATCH v2] x86/mce: Distirbute the clear operation of mces_seen to Per-CPU rather than only monarch CPU Chen Yucong
2014-05-20 17:33 ` Borislav Petkov
2014-05-21 0:48 ` Chen Yucong
2014-05-21 1:33 ` Chen Yucong
2014-05-21 1:40 ` Hidetoshi Seto
2014-05-21 2:03 ` Chen Yucong
2014-05-21 2:43 ` Hidetoshi Seto [this message]
2014-05-21 3:19 ` Chen Yucong
2014-05-21 3:36 ` Hidetoshi Seto
2014-05-21 21:09 ` Luck, Tony
2014-05-23 1:32 ` Chen Yucong
2014-05-23 9:10 ` Borislav Petkov
2014-05-23 11:57 ` Chen Yucong
2014-05-23 22:40 ` Tony Luck
2014-05-23 21:50 ` Tony Luck
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=537C12BC.6080408@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slaoub@gmail.com \
--cc=tony.luck@intel.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