LKML Archive on
help / color / mirror / Atom feed
From: Andi Kleen <>
To: Wink Saville <>
Subject: Re: [PATCH 1/3] Documention for trace records (trec).
Date: 27 Mar 2007 17:19:02 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Wink Saville <> writes:

> Trec is a light weight tracing mechanism that places
> trace information into a buffer. The contents of the
> buffer is dumped when errors occurs or when enabled
> via SYSRQ commands.

relayfs was supposed to fill this purpose. Why do you want
another one?

It doesn't work for sysrq dumping on fatal errors, but in my 
experience on such cases custom tracing is best.


      parent reply	other threads:[~2007-03-27 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24 23:51 Wink Saville
2007-03-24 23:51 ` [PATCH 2/3] Trec driver Wink Saville
2007-03-24 23:51   ` [PATCH 3/3] Initialize and use trec_snapshot and trec_print_snapshot Wink Saville
2007-03-25 19:17   ` [PATCH 2/3] Trec driver Randy Dunlap
2007-03-25 19:23 ` [PATCH 1/3] Documention for trace records (trec) Randy Dunlap
2007-03-27 15:19 ` Andi Kleen [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:

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

  git send-email \ \ \ \ \
    --subject='Re: [PATCH 1/3] Documention for trace records (trec).' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).