All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: combine per-cpu trace files
Date: Mon, 24 Feb 2014 16:22:47 +0100	[thread overview]
Message-ID: <530B63C7.30103@broadcom.com> (raw)
In-Reply-To: <20140224083631.192868c0@gandalf.local.home>

On 02/24/2014 02:36 PM, Steven Rostedt wrote:
> On Mon, 24 Feb 2014 13:07:50 +0100
> Arend van Spriel <arend@broadcom.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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


      reply	other threads:[~2014-02-24 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 12:07 combine per-cpu trace files Arend van Spriel
2014-02-24 13:36 ` Steven Rostedt
2014-02-24 15:22   ` Arend van Spriel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=530B63C7.30103@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.