| 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
| ||
|
Message-ID: <530B63C7.30103@broadcom.com> Date: Mon, 24 Feb 2014 16:22:47 +0100 From: Arend van Spriel <arend@...adcom.com> To: Steven Rostedt <rostedt@...dmis.org> CC: <linux-kernel@...r.kernel.org> Subject: Re: combine per-cpu trace files On 02/24/2014 02:36 PM, Steven Rostedt wrote: > On Mon, 24 Feb 2014 13:07:50 +0100 > Arend van Spriel <arend@...adcom.com> wrote: > >> Hi Steven, >> >> Regarding trace-cmd I have a question about the trace files. While >> debugging an driver issue I had trace-cmd recording driver events on the >> target system until it crashed and I had to power down the machine. Now >> I have three trace-cmd files: trace.dat, trace.cpu1 and trace.cpu2. >> trace-cmd combines the per-cpu files into final trace.dat, but would it >> be possible to do that as a separate post process after a crash/abort. > > Yep, if you installed the trace-cmd man pages (make install_doc) then > do a "man trace-cmd-restore" Nope. But I have a cloned repo so I think I will manage ;-) Thanks, Arend > -- Steve > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists