From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932258AbbFYBAD (ORCPT ); Wed, 24 Jun 2015 21:00:03 -0400 Received: from smtprelay0020.hostedemail.com ([216.40.44.20]:59757 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753363AbbFYA74 (ORCPT ); Wed, 24 Jun 2015 20:59:56 -0400 X-Session-Marker: 726F737465647440676F6F646D69732E6F7267 X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,rostedt@goodmis.org,:::::::,RULES_HIT:41:355:379:541:599:800:960:973:982:988:989:1260:1277:1311:1313:1314:1345:1359:1437:1515:1516:1518:1534:1540:1593:1594:1711:1730:1747:1777:1792:2393:2553:2559:2562:2693:2895:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3868:3871:3872:3873:3874:4043:5007:6261:7875:8603:10004:10400:10848:10967:11232:11658:11914:12114:12296:12517:12519:12740:13069:13138:13231:13311:13357:14096:14097:21080,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0 X-HE-Tag: truck14_90b3e5ea7881c X-Filterd-Recvd-Size: 1718 Date: Wed, 24 Jun 2015 20:59:53 -0400 From: Steven Rostedt To: "Luck, Tony" Cc: bp@suse.de, 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: <20150624205953.57ad77f1@gandalf.local.home> In-Reply-To: <20150624215649.GA16000@agluck-desk.sc.intel.com> References: <20150624215649.GA16000@agluck-desk.sc.intel.com> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 24 Jun 2015 14:56:49 -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. It comes down to if the rasdaemon (and any other user) included the event_parse.c "library" (it's not a public library yet, and we really should make it one). Because if it did, it doesn't matter what the field is, the event descriptions will give the size, and as long as the name of a field exists, and it doesn't change type (that is, from integer to string), it should be fine. -- Steve