From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752001AbbFXWRv (ORCPT ); Wed, 24 Jun 2015 18:17:51 -0400 Received: from cantor2.suse.de ([195.135.220.15]:37511 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750868AbbFXWRn (ORCPT ); Wed, 24 Jun 2015 18:17:43 -0400 Date: Thu, 25 Jun 2015 00:17:28 +0200 From: Borislav Petkov To: "Luck, Tony" Cc: Steven Rostedt , linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: changing format/size of data in TRACE_EVENT(extlog_mem_event) Message-ID: <20150624221728.GJ32642@pd.tnic> References: <20150624215649.GA16000@agluck-desk.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20150624215649.GA16000@agluck-desk.sc.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 24, 2015 at 02:56:49PM -0700, Luck, Tony wrote: > So the question is - how can we update the trace event to include these > new wider fields with the minimum pain to applications that look at it? > I don't know if there are any other consumers besides rasdaemon at the > moment ... but we don't want ugly transitions where you have to guess > which version of the application you need to run to work with a given > kernel version. Well, can we issue an UEFI version and a binary blob which gets unpacked in userspace depending on that version? Can tracepoints even do that? Because the next time they change the spec, we're going to have to deal with that PITA all over again... And if we're going to change the tracepoint now, we better change it only once but in a way that can accomodate future changes... -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --