Target channel of state dumps

Hi,

my customer pointed out some oddity of the hybrid mode: Names of
long-living process (ie. at least those that exist during the full trace
period) are not known to lttv.

I dug deeper and learned that the initial state dumps, like those issued
via list_process_state, go to the cpu channel by default and will thus
be quickly overwritten. Reprogramming the target channel of
list_process_state solves this for me:

echo "set_channel list_process_state default 0 processes" > /proc/ltt

And the above includes a second "oddity": The actual "set_channel"
syntax does not meet the intended one as documented (only!) in the
source code. Will check later if I can provide a patch for this.

But back to the actual issue: Isn't redirecting those state dumps to the
channels under control/ the original intension? If so, should I fix up
ltt-armall? What about redirecting exec events to "processes", in order
to learn also about new threads over the trace runtime? I thought that
this is what the hybrid mode is about, right?

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux