From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] ltt_trace_system_description
Date: Mon, 24 Aug 2009 10:34:23 -0400 [thread overview]
Message-ID: <20090824143423.GB21110@Krystal> (raw)
In-Reply-To: <9FC357E76048C74C93F3BD3D69A16B880284B614@nova.ott.qnx.com>
* David Cummings (DCummings at qnx.com) wrote:
> I was trying to call ltt_trace_system_description from an LTTV module
> but it does not seem to implemented in the latest version of LTTV. I
> noticed that in the modules that do call ltt_trace_system_description
> (such as textDump), the code is commented out and surrounded by a
> FIXME. Is there a particular reason as to why this call is not
> implemented? Are there other mechanisms provided to access this data?
>
This data was planned in the initial LTTV versions, but did depend on
grabbing system information from a /proc text file. I removed this so
that we do not even depend on /proc being active or mounted on the
system, so all the information can be extracted through LTTng channels.
So if we implement something like ltt_trace_system_description, we would
have to export more information from the kernel through the standard
LTTng tracing infrastructure.
Mathieu
> Thanks,
> David Cummings
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
prev parent reply other threads:[~2009-08-24 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 20:45 David Cummings
2009-08-13 20:45 ` David Cummings
2009-08-13 20:45 ` David Cummings
2009-08-24 14:34 ` Mathieu Desnoyers [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:
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=20090824143423.GB21110@Krystal \
--to=compudj@krystal.dyndns.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