Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp866325ybl; Thu, 22 Aug 2019 06:10:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqzzdGniuZc1hv6vLLOs1YIjIEkTVo0UtAkcO2/TJpdHlaQgMRjpILngCfBQYDTkB/BosisF X-Received: by 2002:a62:7513:: with SMTP id q19mr43183586pfc.192.1566479408821; Thu, 22 Aug 2019 06:10:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566479408; cv=none; d=google.com; s=arc-20160816; b=dAl8QwyCMWkRSW+PFCOlZHIj/HcQLcWdRRH4Ha1uKYe5nPU5zJH5p3w8BOiQpSJncR ZP1EANi0ompx2sUJTz1BtGkLCkGIkKkAgFMKs8Y88zIi2ku2dH/n07T4jwJeK5KXOA2E gN2kjTin81x/38Awq7CcBUzsZ/ff22vYGd2d1tOUKEdEzbPtNLxDdZOOnDBPfIyjo2Pc fvsLxiVZUGzK0tykhBCk5kWNIDsLx4RohKLX/ha0LqltTUz00PlOvdKe/oM34ZLvK9/X C7lm8HhRXDlguZor0dpPNpXmUUCBAmDdh89gv2GqUsHUfaa5HaT9g0eMmrtuRUmlVeWI /+pA== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=JKikXsSoOkOv+D0at8KjbVDWFcKg+UtT4qwiMbH7hXk=; b=kvl5FR2txtBtRuzp2Ne7OVnRdEM7ffVDKRBWpmC8ryoDTpd/1Ok1pi/nId1M7Qyd2s UOWic0HM3ZB8W4mH4geierbhMyZOGrNdWUHGpd9NH7mWojjpn+nYsoAjNob8RL0qhAfS vkdnUeTUgLZoh3hEOLepCMmpSB/yj4q+aD5CoyVbeOb1bWcCAMf55k0EvI3XSBFOMple 251iIrbML/TVT/l96fEjmk1tv0VkckpazaT9Xo2QOsaVDEZHxjQL6y/vpfzJsGMAWmcA 7jFM2sXVxMdpHeNMReYQxElekuMJzPsRyUygOltgLwN6iIxt2oj5LMuf5tQKPP+E+c7S H3Dg== ARC-Authentication-Results: i=1; mx.google.com; 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 w18si17127253pll.132.2019.08.22.06.09.53; Thu, 22 Aug 2019 06:10:08 -0700 (PDT) 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; 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 S1732234AbfHVJqL (ORCPT + 99 others); Thu, 22 Aug 2019 05:46:11 -0400 Received: from tartarus.angband.pl ([54.37.238.230]:54268 "EHLO tartarus.angband.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732208AbfHVJqL (ORCPT ); Thu, 22 Aug 2019 05:46:11 -0400 Received: from kilobyte by tartarus.angband.pl with local (Exim 4.92) (envelope-from ) id 1i0jfT-0005ry-CC; Thu, 22 Aug 2019 11:46:07 +0200 Date: Thu, 22 Aug 2019 11:46:07 +0200 From: Adam Borowski To: Borislav Petkov Cc: "Ghannam, Yazen" , "linux-edac@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v3 0/8] AMD64 EDAC fixes Message-ID: <20190822094607.GA14667@angband.pl> References: <20190821235938.118710-1-Yazen.Ghannam@amd.com> <20190822005020.GA403@angband.pl> <20190822083548.GA11646@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190822083548.GA11646@zn.tnic> X-Junkbait: aaron@angband.pl, zzyx@angband.pl User-Agent: Mutt/1.10.1 (2018-07-13) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kilobyte@angband.pl X-SA-Exim-Scanned: No (on tartarus.angband.pl); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 22, 2019 at 10:35:48AM +0200, Borislav Petkov wrote: > On Thu, Aug 22, 2019 at 02:50:20AM +0200, Adam Borowski wrote: > > While you're editing that code, could you please also cut the spam if ECC is > > actually disabled? For example, a 2990WX with non-ECC RAM gets 1024 lines; > > Patch is in there. I'll give you extra points if you spot it. Yeah, some of messages are no longer emitted for memory-less nodes (NUMA 1 and 3). Your patch set also overhauls the messages. But, the amount of redundant messages I'm complaining about has actually increased: dmesg|grep EDAC|cut -c 16-|sort|uniq -c 256 EDAC MC: UMC0 chip selects: 256 EDAC MC: UMC1 chip selects: 1 EDAC MC: Ver: 3.0.0 128 EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. ^ three lines each 64 EDAC amd64: F17h detected (node 0). 64 EDAC amd64: F17h detected (node 1). 64 EDAC amd64: F17h detected (node 2). 64 EDAC amd64: F17h detected (node 3). 512 EDAC amd64: MC: 0: 0MB 1: 0MB 256 EDAC amd64: MC: 2: 0MB 3: 0MB 256 EDAC amd64: MC: 2: 8192MB 3: 0MB 64 EDAC amd64: Node 0: DRAM ECC disabled. 64 EDAC amd64: Node 2: DRAM ECC disabled. 256 EDAC amd64: using x4 syndromes. (Full dmesg at http://ix.io/1T1o) While on 5.3-rc5 without the patchset I get: 1 EDAC MC: Ver: 3.0.0 256 EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. ^ three lines each 64 EDAC amd64: Node 0: DRAM ECC disabled. 64 EDAC amd64: Node 1: DRAM ECC disabled. 64 EDAC amd64: Node 2: DRAM ECC disabled. 64 EDAC amd64: Node 3: DRAM ECC disabled. So I wonder if we could deduplicate those. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can. ⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener. ⠈⠳⣄⠀⠀⠀⠀ A master species delegates.