All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jason Behmer <jbehmer@google.com>
Cc: tom.zanussi@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: Nested events with zero deltas, can use absolute timestamps instead?
Date: Fri, 24 May 2019 11:54:28 -0400	[thread overview]
Message-ID: <20190524115428.2bf41725@gandalf.local.home> (raw)
In-Reply-To: <CAMmhGqK7LxvR2t=v3NY5Um+EPurtbSfkpPtCAhDagFs_Sz0Kuw@mail.gmail.com>

On Fri, 24 May 2019 08:48:44 -0700
Jason Behmer <jbehmer@google.com> wrote:

> Sorry, I'm not sure I follow.  By new tracing option do you mean a new
> option in the timestamp_mode file?  I guess in that case would that
> still be the only writable option?  You could write 1/0 to the file
> which would turn on/off force_absolute_timestamps, and reading the
> file would show which of absolute, delta, and force_absolute was set?
> Or did you mean something else by tracing option?

I mean the options in tracefs/options/*

Do a search for OVERWRITE in kernel/trace/ and see what it does.

-- Steve

  reply	other threads:[~2019-05-24 15:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMmhGqKc27W03roONYXhmwB0dtz5Z8nGoS2MLSsKJ3Zotv5-JA@mail.gmail.com>
2019-03-29 16:52 ` Nested events with zero deltas, can use absolute timestamps instead? Steven Rostedt
2019-04-01 22:54   ` Jason Behmer
2019-04-02  2:20     ` Steven Rostedt
2019-04-02  4:42       ` Jason Behmer
2019-05-24 14:17         ` Jason Behmer
2019-05-24 15:00           ` Steven Rostedt
2019-05-24 15:11             ` Jason Behmer
2019-05-24 15:24               ` Steven Rostedt
2019-05-24 15:48                 ` Jason Behmer
2019-05-24 15:54                   ` Steven Rostedt [this message]
2019-05-24 15:58                     ` Steven Rostedt

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=20190524115428.2bf41725@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=jbehmer@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.zanussi@linux.intel.com \
    /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.