[<prev] [next>] [day] [month] [year] [list]
Message-ID: <036f5f6f2d8a4a768309b61540857393@zhaoxin.com>
Date: Thu, 30 May 2019 03:50:39 +0000
From: Tony W Wang-oc <TonyWWang-oc@...oxin.com>
To: "tipbot@...or.com" <tipbot@...or.com>,
"ashok.raj@...el.com" <ashok.raj@...el.com>
CC: "bp@...e.de" <bp@...e.de>, "hpa@...or.com" <hpa@...or.com>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>,
"mingo@...nel.org" <mingo@...nel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"tony.luck@...el.com" <tony.luck@...el.com>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
David Wang <DavidWang@...oxin.com>
Subject: Re: [tip:x86/urgent] x86/mce: Ensure offline CPUs don' t participate
in rendezvous process
Hi Ashok,
I have two questions about this patch, could you help to check:
1, for broadcast #MC exceptions, this patch seems require #MC exception errors
set MCG_STATUS_RIPV = 1.
But for Intel CPU, some #MC exception errors set MCG_STATUS_RIPV = 0
(like "Recoverable-not-continuable SRAR Type" Errors), for these errors
the patch doesn't seem to work, is that okay?
2, for LMCE exceptions, this patch seems require #MC exception errors
set MCG_STATUS_RIPV = 0 to make sure LMCE be handled normally even
on offline CPU.
For LMCE errors set MCG_STAUS_RIPV = 1, the patch prevents offline CPU
handle these LMCE errors, is that okay?
Thanks
Tony W Wang-oc
Powered by blists - more mailing lists