Received: by 10.223.185.116 with SMTP id b49csp6389508wrg; Wed, 28 Feb 2018 08:37:00 -0800 (PST) X-Google-Smtp-Source: AH8x227/M02HWbDVy7Ue4dRI2NvI9ptvHxKyZCE/8radbwPtJP/mntZaEFsrSyhe51rq63zHG0Xt X-Received: by 10.101.78.5 with SMTP id r5mr13162995pgt.33.1519835820857; Wed, 28 Feb 2018 08:37:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519835820; cv=none; d=google.com; s=arc-20160816; b=bcMh5DXIatOcx+01svJpCDwQo2jvQyQJHz8cz6fH6OZBhbploNsaBwsAqfuxh1h0ad vPzRL09E4rkePoAvnefCA1eQjaTbwlQ2bNVzxcCNXmzoR+91ZUwQpc2D9qZGQxwGOjbZ eu+kaBZ8S4OfIOFe7CcUSGkwIoXa0h31Fm+AJKFy+GnyPXN9Zg1A0L/iII7hqYk8p+Sl p/HDBIGvquyJX29gFlc2SOJ4l2Od+8Vmo8v8RcqEbOMa0b9aX4pRObGLMgKNEBWHjKlo 0bSyE+pV2xqNxHUsyXTBh1h+IBxEk2iT+mqJeE4vU4DOSFgew1NLx88NrO9+KS5BgJjq GpVA== 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 :arc-authentication-results; bh=EH2HvS9znqDXEC8SNYTmru08qsP5/ootZxOFLh2taXo=; b=EpeqVwG52w3IizIcrbcHJCwwGpFUaypQGcGbj6aOLbLTY8dHIE3jMiuSlVUIlqK9R2 3vfLemgjEnssqq/LTGKwck38dN4MgperhbZecWdiFf6dZxtpc9isbu1PeywFbp3jMrNI Qa9p0giv1V4MSlp5GGrcDxr4jRAq6A1eYJLHxXNjvRJqJNQHUL0VlkD7GvzCEJoGypYY TaAvn9UaR0S8mQ0L7v3sYgsAowpwgJm5gKqb5PHPtSljvDim+yd6Pkt2UeDk2ERGdEQP h7AZLgkot3BJv3y6Nv6J5YnJGcsbq46FJEyXrJ8Sntu00wrAPjQTkDEFNsOLnkLJj6VS x2NA== 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 z96-v6si1511421plh.35.2018.02.28.08.36.45; Wed, 28 Feb 2018 08:37:00 -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; 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 S934527AbeB1QgI (ORCPT + 99 others); Wed, 28 Feb 2018 11:36:08 -0500 Received: from mx2.suse.de ([195.135.220.15]:57606 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932656AbeB1QgG (ORCPT ); Wed, 28 Feb 2018 11:36:06 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 5FC2FACB2; Wed, 28 Feb 2018 16:36:04 +0000 (UTC) Date: Wed, 28 Feb 2018 17:35:39 +0100 From: Borislav Petkov To: "Ghannam, Yazen" Cc: Tony Luck , "linux-efi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "ard.biesheuvel@linaro.org" , "x86@kernel.org" Subject: Re: [PATCH v2 0/8] Decode IA32/X64 CPER Message-ID: <20180228163539.GC2969@pd.tnic> References: <20180226193904.20532-1-Yazen.Ghannam@amd.com> <20180228084321.GA2969@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 28, 2018 at 03:12:09PM +0000, Ghannam, Yazen wrote: > CPER is the format used for BERT, etc. We'll only ever see a CPER if the > firmware creates it. And it's up to firmware policy what is shared with > the OS. Yap, but we should still tie it into our infra. > My main reason for printing all the info is that it may be too difficult or too > late to gather that info after the fact. I think this is especially true for boot > errors, though maybe there's another way that I don't know about > (re-reading BERT later?). So that BERT thing is a table, AFAIR. I don't see why it would be a problem if we read it later, at our leisure and free the record only when we're done. Looking at bert.c is entered with a late_initcall() which is nicely late and we have everything up and ready to process errors then. > Right. I want to work on getting this more integrated with our existing > x86 infrastructure. But I don't want to wait until we figure all that out > before we have some sort of CPER decoding. Just keep in mind that whenever you expose stuff and userspace starts using it, it is much harder to change it. So let's do it right pls. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --