[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB60837F3079308E3ACF7EC5ADFCCB2@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Wed, 5 Mar 2025 22:33:04 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Shuai Xue <xueshuai@...ux.alibaba.com>, Borislav Petkov <bp@...en8.de>,
"Yazen.Ghannam@....com" <yazen.ghannam@....com>
CC: "nao.horiguchi@...il.com" <nao.horiguchi@...il.com>, "tglx@...utronix.de"
<tglx@...utronix.de>, "mingo@...hat.com" <mingo@...hat.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>, "x86@...nel.org"
<x86@...nel.org>, "hpa@...or.com" <hpa@...or.com>, "linmiaohe@...wei.com"
<linmiaohe@...wei.com>, "akpm@...ux-foundation.org"
<akpm@...ux-foundation.org>, "peterz@...radead.org" <peterz@...radead.org>,
"jpoimboe@...nel.org" <jpoimboe@...nel.org>, "linux-edac@...r.kernel.org"
<linux-edac@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
"baolin.wang@...ux.alibaba.com" <baolin.wang@...ux.alibaba.com>,
"tianruidong@...ux.alibaba.com" <tianruidong@...ux.alibaba.com>
Subject: RE: [PATCH v2 2/5] x86/mce: dump error msg from severities
>>> 2) I'd like to see a patch for a stack trace for the unrecoverable case.
>>
>> Could you provide any reference link to your previous patch?
>
> https://lore.kernel.org/all/20220922195136.54575-1-tony.luck@intel.com/
Yazen has some cleanups to the severity code under consideration
here:
https://github.com/AMDESE/linux/commit/cf0b8a97240abf0fbd98a91cd8deb262f827721b
I wonder if a slightly different approach with the "mce_action" that Yazen
defines being a bitmask of options, instead of an enum, would be possible?
If that happened, then adding a "dump the call stack to the console" option
would fit neatly into the scheme.
-Tony
Powered by blists - more mailing lists