Received: by 10.223.185.116 with SMTP id b49csp1349063wrg; Sun, 11 Feb 2018 09:57:21 -0800 (PST) X-Google-Smtp-Source: AH8x227MpRAd0cIg3+eXi67GZnZED5laoqlrhVO81i0bXgyRb6d8phaCeHE7ICNZEkFVgYAbxwMi X-Received: by 10.101.90.78 with SMTP id z14mr7619689pgs.215.1518371841471; Sun, 11 Feb 2018 09:57:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518371841; cv=none; d=google.com; s=arc-20160816; b=u3B8nGUytxQ2sBDqCDFQ7pqjfbvnuBwYu/orIm5bjO2oGGWcuqutFQ/Z1t0IBW0rKF 7OrJcICRdsi6O6z1IkaJa+DS7/SK+iF1gZaRcSkuOrfquS1KJQRi0q5dnKW1CZEz3pC5 UVcz4VX+J9Fk3mulLz4S4ORBupzH7M9duuV8Oe7jnpcKJPRCccVwDck6JQI/woIFYuor X721Ohr0p+XCrNu6lh0Osi34Ws5L0yMYfPpfmVnnFP5GMmjiw19o/KCLB0IYLnOSPxzF /aKrkn6UBGbTeUCh/Ny/oa3kOJk3Bf1YJUIro7nOUfKb0u7T45gOvsIY9Y1KH2scdbrg mUwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=Y0Y2UHXCXEIEhwP+fsul0aodXLATXGy5MYE52MjXc/Q=; b=uMw+7dA7i8s/SfH+W8V31XFxp6/ywsqaudrBSWlfMJt/dBVETsI+EsBbiTUC7EHuRl hi8pwe0TEAD6OrOHznsLBXj8WeMnq9vPuRQaDpk1hVFaYzA2k7UyD0gSy76RV8E3czbC WnKKLFaL544RBObJ0Jg4KI7Xd06OdRW/nUhgHJYMD0RlARku2KNzJLLOPA6ITd0zHkJj xY19e0LLBXchFel9F8MJenH4TPq5faB075G2WvgGWkCoC4HjkDcss1gu0vqbetvbHNBK cZKf81z+Mg/pvYUYD/l+YvvG6GSit1cJBToe3BiBbE4O8fSCEIhmrpy1fXslJpQdxNzQ YMPg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=WESOnitb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d189si1373121pgc.664.2018.02.11.09.57.06; Sun, 11 Feb 2018 09:57:21 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=WESOnitb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753579AbeBKR42 (ORCPT + 99 others); Sun, 11 Feb 2018 12:56:28 -0500 Received: from mail-oi0-f68.google.com ([209.85.218.68]:44860 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753524AbeBKR41 (ORCPT ); Sun, 11 Feb 2018 12:56:27 -0500 Received: by mail-oi0-f68.google.com with SMTP id b3so9556951oib.11; Sun, 11 Feb 2018 09:56:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Y0Y2UHXCXEIEhwP+fsul0aodXLATXGy5MYE52MjXc/Q=; b=WESOnitbLEJX2fiUgwKjl/mhmc2VFEQqFP0Vz2WJOd6l9rqXV0a1Rp6lBO9V1P96Ax bGC1pkgKYOyyFLSCQp/0cWWICBGmnu+IkJrXsJ9SwVK9ZNoCVRllX9hZ1IGvGxSVv+ch 4vKLpnpVmt9BDdjfIKb80OePlpxXOiUPzmWXG2P7ZX1FV6NdmkWO2PEMvpsFDD6Soac4 mR4VJZGfAzuml1s6Wt0dGt2x01mBHLUzMlg9mRxUlHzSKDF4jCC//lIoVjJ1Tv3kZCQ4 SdoVxmy2svnb8DbmRn1I0YC9KHsHoGTjjWjfC6R2FyVaLf0AlLyl/+gwChCXtjgmSQ6G Jb+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=Y0Y2UHXCXEIEhwP+fsul0aodXLATXGy5MYE52MjXc/Q=; b=Uc7rOdwYQhw5imMZ9x1ugiLE29DJPJBwl70LrhUhe6fatollvmzrxoHRXKHNS6j1wN rajAwc5HPiKfJKHgCw9NHl78/f9qazPgdK+bioJ+6PTCaNt1msy6nF9yGIWw229fzQDo QnclAhxMNyGkEuq5+c8EFwt6I4fCx7Up5NF1aMe8W1LAgVzgLNXLJrmHV6ozKrn79Wxi MtuPvkjbh3b8Dut6DvxjyG0MK2Kkhzs4mx+/u7cbaH926Sr4Tk5rPjGn8E1pvUtGlk+f sPKHqSGKRPkFPifLkAGaCKKWRJegfY72q8hDQFQmkDRh0pVJKHzBawgWIighuJIGWXpT WxJg== X-Gm-Message-State: APf1xPCTw9P1xZdqTuqywbkvGphWT75hRHZhl42vm5RP0yixlhdtsuxj yTqhWRHTSnP1ystP7HKogtU= X-Received: by 10.202.107.194 with SMTP id g185mr6629679oic.268.1518371786621; Sun, 11 Feb 2018 09:56:26 -0800 (PST) Received: from localhost (108-223-40-66.lightspeed.sntcca.sbcglobal.net. [108.223.40.66]) by smtp.gmail.com with ESMTPSA id a44sm4079639ote.72.2018.02.11.09.56.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 11 Feb 2018 09:56:26 -0800 (PST) Date: Sun, 11 Feb 2018 09:56:25 -0800 From: Guenter Roeck To: Jerry Hoemann Cc: wim@linux-watchdog.org, linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org, rwright@hpe.com, maurice.a.saldivar@hpe.com Subject: Re: [01/10] watchdog/hpwdt: Remove legacy NMI sourcing. Message-ID: <20180211175625.GA22035@roeck-us.net> References: <20180206225855.30582-2-jerry.hoemann@hpe.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180206225855.30582-2-jerry.hoemann@hpe.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 06, 2018 at 03:58:46PM -0700, Jerry Hoemann wrote: > Gen8 and prior Proliant systems supported the "CRU" interface > to firmware. This interfaces allows linux to "call back" into firmware > to source the cause of an NMI. This feature isn't fully utilized > as the actual source of the NMI isn't printed, the driver only > indicates that the source couldn't be determined when the call > fails. > > With the advent of Gen9, iCRU replaces the CRU. The call back > feature is no longer available in firmware. To be compatible and > not attempt to call back into firmware on system not supporting CRU, > the SMBIOS table is consulted to determine if it is safe to > make the call back or not. > > This results in about half of the driver code being devoted > to either making CRU calls or determing if it is safe to make > CRU calls. As noted, the driver isn't really using the results of > the CRU calls. > > As the CRU sourcing of the NMI isn't required for handling the > NMI, remove the legacy (pre Gen9) NMI sourcing and the DMI code to > determine if the system had the CRU interface. > > Signed-off-by: Jerry Hoemann > Reviewed-by: Guenter Roeck Spoke too early. This fails to compile if CONFIG_HPWDT_NMI_DECODING is disabled. Please fix and resubmit the series, and please make sure that each patch compiles on its own. Thanks, Guenter