Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2160415yba; Fri, 17 May 2019 11:32:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqzfQ215mI92vMEXN5ipZL7DYkoKdhbRCmN6IES1parLpXK5jME45o5VMrEJ9JdlHdaKlGXM X-Received: by 2002:a17:902:158b:: with SMTP id m11mr16988069pla.268.1558117976908; Fri, 17 May 2019 11:32:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558117976; cv=none; d=google.com; s=arc-20160816; b=gO1ILkaXwMCoNMCLMs1pstimer2bCm5Pm1B1uQk6imR7RwowMeckplVEWuP8WM6MDj X+YedwvgC+VotSsnD1JlWQFpyt6Bd+9NOD+KEGt4NGyuAUG45jin+HFuKf6ViUbPvMIo vMgLy8cEE0D2DZOLCWGQAPmVjwfwiozAUihOdeSGz+P/wMY3N3xjbNrcpCmwAoF64yvb mM3Vqv1+4QBPvdiZXZUUZWqjurMzHLIMS1hSHiVAcP5VICvZstu3UmTq2wBv8hPt+VHG g/QGfKh8I6wrWX0h70MH2iXr8yDDWGVL7BzmwBJa0HjO00IjcLYn7iAd3Zfv1PnAWKWQ hz5g== 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=R+DLA5iRGQqWnyGYcrpwBxvt4tXhyqLm8zmuwC1fXXw=; b=XZ4QbSokVXADp4tb8c4t6EiUuKNu+miZJ10fXtAbnSpNirW1XaFfilKp1NyXnvBeZ/ KPzaU1rvOSuFFEWkhj+FzXklYPNeAgqSWp8ZUqfztqkSpGGh4MpKlpxndvGJtP7ndOmg VI26CudBNmp5mpRcUvwaYA5Ow6aH3JBj34/rMkCg3JJp0qE+9/KIwHba87GjiITIENiw HLvw+l3a8QthY6uvMVi9C8Ckt6frOpyuKsz8RXIgcictKtIPeMq+Mf1VK4O5P4g2stW2 mYxs/37RGMIzpoC2OrCDHxS2ijgELeLWs2pIJSwMm7tqQOM0Q0xFNj12xiljX3B+Lt4a Djxw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b=LeIHLkPl; 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 k5si4129453pgc.322.2019.05.17.11.32.39; Fri, 17 May 2019 11:32:56 -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; dkim=pass header.i=@alien8.de header.s=dkim header.b=LeIHLkPl; 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 S1727088AbfEQQhe (ORCPT + 99 others); Fri, 17 May 2019 12:37:34 -0400 Received: from mail.skyhub.de ([5.9.137.197]:49620 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725932AbfEQQhd (ORCPT ); Fri, 17 May 2019 12:37:33 -0400 Received: from zn.tnic (p200300EC2F0C50007C4D1753FB652448.dip0.t-ipconnect.de [IPv6:2003:ec:2f0c:5000:7c4d:1753:fb65:2448]) (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 4E1381EC06AC; Fri, 17 May 2019 18:37:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1558111051; 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=R+DLA5iRGQqWnyGYcrpwBxvt4tXhyqLm8zmuwC1fXXw=; b=LeIHLkPlhv3/cBmM4ttLviR6CNztW9aHS4gyALN/6R0SGSUIJUoqbLM2K2cy0fFYI9xW7y z3uFEWqGq4pcOoCHnW5WVGXNyroLhWwqkqdjjddNIBp6V4rvSFk4KEAV1UQWDahTv/hqWu /U4bLKURpbilaUq4tRDd4MXirrl5+SE= Date: Fri, 17 May 2019 18:37:29 +0200 From: Borislav Petkov To: "Ghannam, Yazen" Cc: "Luck, Tony" , "linux-edac@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "x86@kernel.org" Subject: Re: [PATCH v3 5/6] x86/MCE: Save MCA control bits that get set in hardware Message-ID: <20190517163729.GE13482@zn.tnic> References: <20190516155202.GA11517@agluck-desk> <20190516165648.GB21857@zn.tnic> <20190516172117.GC21857@zn.tnic> <20190516203456.GD21857@zn.tnic> <20190516205943.GA3299@agluck-desk> <20190517101006.GA32065@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 Fri, May 17, 2019 at 03:46:07PM +0000, Ghannam, Yazen wrote: > I think there are a couple of issues here. > 1) The bank is being initialized without accounting for any quirks. Almost. __mcheck_cpu_init_clear_banks() a little bit later corrects that. I guess I can drop the wrmsrl(msr_ops.status(i), 0); in here because __mcheck_cpu_init_clear_banks() does that too. Now, the wrmsrl(msr_ops.ctl(i), -1) rdmsrl(msr_ops.ctl(i), val); method of throwing all 1s to see what sticks is what Intel wants, as Tony said. Is that going to be a problem on AMD? > 2) The bank is being initialized without having set up any handler or > other appropriate setup. I'm afraid you're going to have to explain this in more detail... -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.