Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp605766ybi; Fri, 26 Jul 2019 15:49:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqyKZ25jtPXsiW2QjFwNIEiZnfrSnpaVKZ1LemYYWfVas5kmFKxKm5y1Ms9CwawcOGIybXu/ X-Received: by 2002:a17:902:e011:: with SMTP id ca17mr100550466plb.328.1564181350753; Fri, 26 Jul 2019 15:49:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564181350; cv=none; d=google.com; s=arc-20160816; b=PyxeH9M+BnTOJG0xHQfUUyhDnfeJyOwkWyglivdWfnO19DQQWQgmCFkFAinfXyAXok lo29rw1KZGQIyUEhw65PA86SHr1vvp4jJds6SWBplLupeB/otkEVthb81nGXBGHyKZ4v xthstR5KA/SMyDyduxeYim34Xn0np/H+upcYhpd8OardC9fk78rTKGrRa8qc4nF37HyC JSwGn2WHrX9XDxPCkg1rMxUYAQKIBc+azwZRa4Hond7YjfPdfBbbaCMXDWqYCg1QUKJg mZIZ9CThOw3SOra6h2+0ErxtH88gPelZ4LGPN4sw0hEvT30uER24uJ1O1GlfFJs1zI+A TI2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=/RCIdQhJz0+GO4bM6u4cG/BIaFvQ8wy+Nvex02GSDJU=; b=fCox/tmXfaLeP3L0Vx+5wy+16d50hotQmuzrStZZwbAknwchcuhtoxfpE+9aUt7NIb Luce0YQtunjSyw4LFFGSOzW6IGjjao909nPYFWjvTvpj7CiFh4GBk3M2gFLM5OADlWcZ rD5QegEdvGBXqzhAYgdrqPh9maPWAkZ9FTdbalBKLKJ9a91fD7uboHwemj8vJnCFnnIu bJnFgVdniK/Ag2ITQc7IFBToIiGOPWMpi6n+ZWuHXEGzMe81wusVIp8yTLgj0r34dgz1 WtUThKB/fX4Dm2rQb7v7dh8kvoG2bTd3tV5OOPDGfcqjdcdIKrhPoyfuJ/hxSDSgPgXs /f9g== 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 d1si6349984pgn.512.2019.07.26.15.48.55; Fri, 26 Jul 2019 15:49:10 -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 S1727348AbfGZVAF (ORCPT + 99 others); Fri, 26 Jul 2019 17:00:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:42768 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726416AbfGZVAF (ORCPT ); Fri, 26 Jul 2019 17:00:05 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 054D022BE8; Fri, 26 Jul 2019 21:00:03 +0000 (UTC) Date: Fri, 26 Jul 2019 17:00:02 -0400 From: Steven Rostedt To: Andres Freund Cc: Arnaldo Carvalho de Melo , LKML , Linux Trace Devel , Tzvetomir Stoyanov , Jiri Olsa , Ingo Molnar , Namhyung Kim Subject: Re: [PATCH] tools/lib/traceevent, tools/perf: Move struct tep_handler definition in a local header file Message-ID: <20190726170002.13bbfbf5@gandalf.local.home> In-Reply-To: <20190726205544.yffnsfsnji362jk7@alap3.anarazel.de> References: <20181005122225.522155df@gandalf.local.home> <20190726035829.4xcw5k2exx4omlvg@alap3.anarazel.de> <20190726091200.0d1e1f01@gandalf.local.home> <20190726205544.yffnsfsnji362jk7@alap3.anarazel.de> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; 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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 26 Jul 2019 13:55:44 -0700 Andres Freund wrote: > How about my proposal to instead change the loops in > trace-event-{python,perl}.c, the only callers of trace_find_next_event, > to be something akin to > > [idx_type_for_tep_get_event] event_count = tep_get_events_count(pevent); > for ([idx_type_for_tep_get_event] idx = 0; idx < event_count; idx++) > { > struct tep_event *event = tep_get_events(...); > > } > > and just removing trace_find_next_event()? It's not a nice API imo, and > seems unnecessary given that the events aren't a linked list anymore. Yep, go for it :-) > > > > Care to send a formal patch? > > Will do. Thanks! -- Steve