From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: rostedt <rostedt@goodmis.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Masami Hiramatsu <mhiramat@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Yordan Karadzhov <y.karadz@gmail.com>,
Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
Tom Zanussi <zanussi@kernel.org>,
Jason Behmer <jbehmer@google.com>,
Julia Lawall <julia.lawall@inria.fr>,
Clark Williams <williams@redhat.com>,
bristot <bristot@redhat.com>, Daniel Wagner <wagi@monom.org>,
Darren Hart <dvhart@vmware.com>, Jonathan Corbet <corbet@lwn.net>,
"Suresh E. Warrier" <warrier@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH] ring-buffer: Have nested events still record running time stamp
Date: Thu, 25 Jun 2020 09:53:15 -0400 (EDT) [thread overview]
Message-ID: <126813531.12266.1593093195147.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20200625094454.732790f7@oasis.local.home>
----- On Jun 25, 2020, at 9:44 AM, rostedt rostedt@goodmis.org wrote:
> From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
>
> [ SEVEN YEAR PROBLEM SOLVED! ]
>
> Up until now, if an event is interrupted while it is recorded by an
> interrupt, and that interrupt records events, the time of those events will
> all be the same. This is because events only record the delta of the time
> since the previous event (or beginning of a page), and to handle updating
> the time keeping for that of nested events is extremely racy. After years of
> thinking about this and several failed attempts, I finally have a solution
> to solve this puzzle.
Out of curiosity, considering that LTTng has solved this problem 10+ years ago
with a simpler concurrency-friendly time-stamping model, why not simply use it
rather than add complexity to the current ftrace timestamp scheme ?
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2020-06-25 13:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 13:44 [RFC][PATCH] ring-buffer: Have nested events still record running time stamp Steven Rostedt
2020-06-25 13:53 ` Mathieu Desnoyers [this message]
2020-06-25 14:37 ` Steven Rostedt
2020-06-25 16:42 ` Korben Rusek
2020-06-25 18:12 ` Steven Rostedt
2020-06-25 17:55 ` Mathieu Desnoyers
2020-06-25 18:35 ` Steven Rostedt
2020-06-25 19:35 ` Mathieu Desnoyers
2020-06-25 19:58 ` Steven Rostedt
2020-06-26 2:36 ` Steven Rostedt
2020-06-26 3:35 ` Steven Rostedt
2020-06-26 13:58 ` Steven Rostedt
2020-06-26 18:13 ` Mathieu Desnoyers
2020-06-26 18:58 ` Steven Rostedt
2020-06-26 19:39 ` Steven Rostedt
2020-06-30 0:21 ` Steven Rostedt
2020-06-30 3:13 ` Mathieu Desnoyers
2020-06-30 3:26 ` Steven Rostedt
2020-06-25 19:04 ` Steven Rostedt
2020-06-25 19:58 ` Mathieu Desnoyers
2020-06-25 20:42 ` Steven Rostedt
2020-06-25 19:09 ` Steven Rostedt
2020-06-25 20:03 ` Mathieu Desnoyers
2020-06-25 18:02 ` kernel test robot
2020-06-25 18:09 ` Steven Rostedt
2020-06-25 18:56 ` kernel test robot
2020-06-26 8:44 ` Dan Carpenter
2020-06-26 8:44 ` Dan Carpenter
2020-06-28 8:59 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2020-06-25 17:10 kernel test robot
2020-06-25 20:43 kernel test robot
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=126813531.12266.1593093195147.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=acme@redhat.com \
--cc=bristot@redhat.com \
--cc=corbet@lwn.net \
--cc=dvhart@vmware.com \
--cc=jbehmer@google.com \
--cc=jolsa@redhat.com \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tz.stoyanov@gmail.com \
--cc=wagi@monom.org \
--cc=warrier@linux.vnet.ibm.com \
--cc=williams@redhat.com \
--cc=y.karadz@gmail.com \
--cc=zanussi@kernel.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.