Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030506AbbDWSAX (ORCPT ); Thu, 23 Apr 2015 14:00:23 -0400 Received: from mga02.intel.com ([134.134.136.20]:8010 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030412AbbDWSAR (ORCPT ); Thu, 23 Apr 2015 14:00:17 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,632,1422950400"; d="scan'208";a="699915087" From: "Luck, Tony" To: Borislav Petkov , Jiri Kosina CC: linux-edac , "Rafael J. Wysocki" , Len Brown , Tomasz Nowicki , "Chen, Gong" , Wolfram Sang , "Zheng, Lv" , "Naoya Horiguchi" , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "Huang, Ying" Subject: RE: [RFC PATCH 5/5] GHES: Make NMI handler have a single reader Thread-Topic: [RFC PATCH 5/5] GHES: Make NMI handler have a single reader Thread-Index: AQHQaG/qBO9fcQF4KE271vujn38g+Z04RDuAgABlg4CAIjzjAIAABYCAgAAhTsA= Date: Thu, 23 Apr 2015 18:00:15 +0000 Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A6446B@ORSMSX114.amr.corp.intel.com> References: <1427448178-20689-1-git-send-email-bp@alien8.de> <1427448178-20689-6-git-send-email-bp@alien8.de> <20150401134913.GB18523@pd.tnic> <20150423085939.GC28340@pd.tnic> In-Reply-To: <20150423085939.GC28340@pd.tnic> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.138] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id t3NI0UIr028492 Content-Length: 346 Lines: 13 > 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 ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?