linux-kernel - Re: [PATCH v1] trace-cmd: introduce --initital-delay for record command

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171218125231.445d8fa2@gandalf.local.home>
Date:   Mon, 18 Dec 2017 12:52:31 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     David Hildenbrand <david@...hat.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Trace Devel <linux-trace-devel@...r.kernel.org>
Subject: Re: [PATCH v1] trace-cmd: introduce --initital-delay for record
 command

On Mon, 18 Dec 2017 17:23:24 +0100
David Hildenbrand <david@...hat.com> 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 <tracer> -e <events> -b <big-buffer-size>
# 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.