From mboxrd@z Thu Jan  1 00:00:00 1970
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Date: Mon, 24 Aug 2009 10:34:23 -0400
Subject: [ltt-dev] ltt_trace_system_description
In-Reply-To: <9FC357E76048C74C93F3BD3D69A16B880284B614@nova.ott.qnx.com>
References: <9FC357E76048C74C93F3BD3D69A16B880284B614@nova.ott.qnx.com>
Message-ID: <20090824143423.GB21110@Krystal>

* 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