Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp1131102ybx; Thu, 7 Nov 2019 07:43:15 -0800 (PST) X-Google-Smtp-Source: APXvYqxAvFII3eSacKveViwaVYTo90qrBMUxcG4PKqpRu35/G9rSmlgYsS142Qs7YqhXfsJcZncO X-Received: by 2002:a50:9850:: with SMTP id h16mr4361415edb.193.1573141394886; Thu, 07 Nov 2019 07:43:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573141394; cv=none; d=google.com; s=arc-20160816; b=VjiKDxSvmu67Y4MCyhnC7pS2LGL3lq20q21Q/nWjRlezsD3yH+t5uAXQTaAqUAak/G g9eyzytW2EYhMVN0rf52BAuA0f3KkBTr9TQAyLlYEG2r2PMwl5eGv9nTwDLzjADwxBPd Vs0I5HklsX594m4qXvY/Vqskyl39c7uNeUeZtCFYwFhHi5SqdmnpK/sI82rvhnA2582W KKaAP+fY1hLcTlKH0JI9CZqkR1fYpwx5FgGwavKVjwQ1u+Mbd13569XM/4ZZkwlUzsmM mvnrOR6EHMHxHV0AdijxNYP/WeLmwR2b5m2wjKvMDmhA5SPWOsWzNmP1HYZFhDHqOFdc WF/A== 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; bh=eAnfQdd7N6fknAtquSRK+MKVOqjcPX9i2EkihseahM4=; b=Beq1FHd//P+yF2Q0ARjxRH/BiJIH8QXVLlxMrhVq3F61ml6QZ0CTMcy5mmdpBrG4vT ztTOUfFmOlzYqX2Eqkd0Xj2QJ5JEXUs9NhVwdG+HSEOtTuc7M5XvYdHkkUzZwJ4fr4t7 cjShbhjgUlVxsy+ODtZW1mEkAfSTo8cn+0RmnRhJr5AvKBUy8PPBb7d/8cP0f37KQjEU ekLVnCe64fR4SKkUSC5iSS+pAa03ukArMJDqb6CxnuFLgbrT/D6b7d9c4zazhy9oP4fW k8xajX7jguNB7Hej/vIyJcYPSUBania/qrBkGqV7RKfbp51wGWf9+CIlSQDeMTB22SmG QsNA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b="J/uXnq5O"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g11si1722836ejx.212.2019.11.07.07.42.50; Thu, 07 Nov 2019 07:43:14 -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=pass header.i=@alien8.de header.s=dkim header.b="J/uXnq5O"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730040AbfKGPkN (ORCPT + 99 others); Thu, 7 Nov 2019 10:40:13 -0500 Received: from mail.skyhub.de ([5.9.137.197]:39036 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726810AbfKGPkM (ORCPT ); Thu, 7 Nov 2019 10:40:12 -0500 Received: from zn.tnic (p200300EC2F0EAD0005075A6AC44F3288.dip0.t-ipconnect.de [IPv6:2003:ec:2f0e:ad00:507:5a6a:c44f:3288]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id C44B21EC0CF7; Thu, 7 Nov 2019 16:40:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1573141207; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=eAnfQdd7N6fknAtquSRK+MKVOqjcPX9i2EkihseahM4=; b=J/uXnq5Opaxro9jWkn9QvvR3qjhsjqEEGuPEbRrhyszkuAqGWUIIrXfa8xW7KHg5a1f9+r EoM1yMK1zzZvt5Ja4YwfvNfdtDsUgMlvKhNms6CsqBVDjy1DxqlxCop/+XmGuD2U1w4eR5 gaQx1BZ6lujT2pAXRmESrOE4ZsDuDhQ= Date: Thu, 7 Nov 2019 16:40:06 +0100 From: Borislav Petkov To: "Ghannam, Yazen" Cc: "linux-edac@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v3 0/5] AMD64 EDAC: Check for nodes without memory, etc. Message-ID: <20191107154006.GF19501@zn.tnic> References: <20191106012448.243970-1-Yazen.Ghannam@amd.com> <20191106160607.GC28380@zn.tnic> <20191106195417.GF28380@zn.tnic> <20191107103857.GC19501@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 07, 2019 at 01:47:53PM +0000, Ghannam, Yazen wrote: > BTW, what do you think about loading based on PCI devices? The module > used to do this. I ask because I'm starting to see that future systems may > re-use PCI IDs, and this indicates the same level of hardware support. The reason we switched to family-based autoloading was that almost every new platform would add a new PCI device ID, which would require enablement work... > Just a nit, but this else seems unnecessary right? Maybe it is easier if you look at the function end in the .c file directly as diffs can be confusing: static bool ecc_enabled(struct amd64_pvt *pvt) { ... amd64_info("Node %d: DRAM ECC %s.\n", nid, (ecc_en ? "enabled" : "disabled")); if (!ecc_en || !nb_mce_en) return false; else return true; } -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette