[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A6446B@ORSMSX114.amr.corp.intel.com>
Date: Thu, 23 Apr 2015 18:00:15 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Borislav Petkov <bp@...e.de>, Jiri Kosina <jkosina@...e.cz>
CC: linux-edac <linux-edac@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <lenb@...nel.org>,
Tomasz Nowicki <tomasz.nowicki@...aro.org>,
"Chen, Gong" <gong.chen@...ux.intel.com>,
Wolfram Sang <wsa@...-dreams.de>,
"Zheng, Lv" <lv.zheng@...el.com>,
"Naoya Horiguchi" <n-horiguchi@...jp.nec.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Huang, Ying" <ying.huang@...el.com>
Subject: RE: [RFC PATCH 5/5] GHES: Make NMI handler have a single reader
> I think we should apply this.
>
> Here's why: nothing in the ghes_notify_nmi() handler does CPU-specific
> accesses
This looks to be true.
> Tony, objections?
No objections.
-Tony
Powered by blists - more mailing lists