From: Steven Rostedt <rostedt@goodmis.org>
To: Ron Rechenmacher <ron@fnal.gov>
Cc: David Ahern <dsahern@gmail.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] tracing: Export key trace event symbols
Date: Wed, 22 Apr 2015 11:44:51 -0400 [thread overview]
Message-ID: <20150422114451.298d8184@gandalf.local.home> (raw)
In-Reply-To: <5537BFF4.1050605@gmail.com>
On Wed, 22 Apr 2015 09:36:20 -0600
David Ahern <dsahern@gmail.com> wrote:
> One of the key requirements is a common time basis (e.g.,
> CLOCK_MONOTONIC or PERF_CLOCK) to be able to merge the events properly.
> I have a kernel module that exports perf_clock to userspace via
> clock_gettime; the 4.1 kernel should have the code that allows the clock
> id to be specified providing a solution to this problem.
Ron,
I should have warned you. This is normal Linux kernel development.
Someone posts a simple patch to make something of there's work better,
and it ends up becoming a massive undertaking to come up with a solution
that makes Linux in general a better operating system ;-)
-- Steve
next prev parent reply other threads:[~2015-04-22 15:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 21:38 [PATCH] tracing: Export key trace event symbols Ron Rechenmacher
2015-04-21 6:10 ` Christoph Hellwig
2015-04-21 12:04 ` Ron Rechenmacher
2015-04-21 12:19 ` Ron Rechenmacher
2015-04-21 13:38 ` Steven Rostedt
2015-04-21 12:22 ` Christoph Hellwig
2015-04-21 13:13 ` Ron Rechenmacher
2015-04-21 13:23 ` Christoph Hellwig
2015-04-21 13:26 ` Ron Rechenmacher
2015-04-21 13:53 ` Steven Rostedt
2015-04-21 15:00 ` Ron Rechenmacher
2015-04-21 15:49 ` Steven Rostedt
2015-04-21 22:23 ` Ron Rechenmacher
2015-04-21 22:44 ` Steven Rostedt
2015-04-22 2:24 ` Ron Rechenmacher
2015-04-22 12:53 ` Steven Rostedt
2015-04-22 12:55 ` Steven Rostedt
2015-04-22 14:47 ` Arnaldo Carvalho de Melo
2015-04-22 15:36 ` David Ahern
2015-04-22 15:44 ` Steven Rostedt [this message]
2015-04-22 16:35 ` Ron Rechenmacher
2015-04-22 17:00 ` Steven Rostedt
2015-04-23 15:28 ` Pawel Moll
2015-04-23 15:33 ` Pawel Moll
2015-04-21 13:31 ` Steven Rostedt
2015-04-24 21:24 ` Steven Rostedt
2015-04-24 21:39 ` Mathieu Desnoyers
2015-04-27 19:12 ` Ron Rechenmacher
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=20150422114451.298d8184@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=arjan@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=pawel.moll@arm.com \
--cc=ron@fnal.gov \
/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 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).