From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752780AbaBXPWv (ORCPT ); Mon, 24 Feb 2014 10:22:51 -0500 Received: from mail-gw3-out.broadcom.com ([216.31.210.64]:3832 "EHLO mail-gw3-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751568AbaBXPWu (ORCPT ); Mon, 24 Feb 2014 10:22:50 -0500 X-IronPort-AV: E=Sophos;i="4.97,535,1389772800"; d="scan'208";a="16109042" Message-ID: <530B63C7.30103@broadcom.com> Date: Mon, 24 Feb 2014 16:22:47 +0100 From: Arend van Spriel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Steven Rostedt CC: Subject: Re: combine per-cpu trace files References: <530B3616.70409@broadcom.com> <20140224083631.192868c0@gandalf.local.home> In-Reply-To: <20140224083631.192868c0@gandalf.local.home> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/24/2014 02:36 PM, Steven Rostedt wrote: > On Mon, 24 Feb 2014 13:07:50 +0100 > Arend van Spriel 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@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >