From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-trace-devel-owner@vger.kernel.org Received: from mail.kernel.org ([198.145.29.99]:36532 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936936AbdLRRwd (ORCPT ); Mon, 18 Dec 2017 12:52:33 -0500 Date: Mon, 18 Dec 2017 12:52:31 -0500 From: Steven Rostedt To: David Hildenbrand Cc: Linux Kernel Mailing List , Linux Trace Devel Subject: Re: [PATCH v1] trace-cmd: introduce --initital-delay for record command Message-ID: <20171218125231.445d8fa2@gandalf.local.home> In-Reply-To: <7b89f63f-3a6f-4182-c26a-934514ba5670@redhat.com> References: <20171218112412.11898-1-david@redhat.com> <20171218104158.22519a7e@gandalf.local.home> <7b89f63f-3a6f-4182-c26a-934514ba5670@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-trace-devel-owner@vger.kernel.org List-ID: On Mon, 18 Dec 2017 17:23:24 +0100 David Hildenbrand wrote: > What I need: Start tracing and flush all buffers when exiting. (e.g. Why don't you use "trace-cmd start" and "trace-cmd extract"? "trace-cmd record" is all about not losing events. If you are creating a big buffer, then I think you want to use this. # trace-cmd start -p -e -b # run test # trace-cmd stop # trace-cmd extract Wouldn't that work for you? -- Steve > after 30 seconds). Never wakeup in between, so the real trace overhead > in that period of time is purely storing the tracepoints to the buffer > in the kernel. Of course we could implement something like that ("copy > from the buffer only when exiting") or try to see if we can fix the > existing "-s" flag in a way that allows it.