From: Johannes Berg <johannes@sipsolutions.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: collecting static data related to tracing
Date: Tue, 18 May 2010 16:09:02 +0200 [thread overview]
Message-ID: <1274191742.31554.10.camel@jlt3.sipsolutions.net> (raw)
Hi,
We've got some tracing in the wireless subsystem that allows us to find
out what's going on quite well. I frequently ask users to use trace-cmd
to record data and send me the resulting file. (Oh and please ... I
don't care if perf could do this as well, trace-cmd works great for me)
However, in all of this I still have to ask users for things like their
hardware and firmware version etc. I also ask for the kernel version,
but that would be easy to simply record in trace-cmd. However, device
versions are very specific to the tracer in use.
I'm thinking that we could have per subsystem "detail" files that are
provided by the respective subsystem implementation in some way, and can
then simply be included in the recorded trace file. However, I have no
idea if that is feasible to implement, or if maybe there's another way.
FWIW, all my events already contain a pointer, used as a cookie, to
identify the hardware instance, but that only allows me to read a trace
that contains data about multiple devices, it doesn't give me
information about each device. Ideally, the "detail" file would list all
the information along with the cookie, so I could connect the dots.
Thoughts?
johannes
next reply other threads:[~2010-05-18 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 14:09 Johannes Berg [this message]
2010-05-18 14:41 ` Steven Rostedt
2010-05-18 14:45 ` Johannes Berg
2010-05-19 7:28 ` Frederic Weisbecker
2010-05-19 8:15 ` Johannes Berg
2010-05-19 14:44 ` 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=1274191742.31554.10.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®