Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [linuxtools-dev] Modeled state in TMF/LTTng

> It's not because the current LTTV state machines differ for cpu state
> and thread state that this is the correct model. The CPU state
> machine has been added by Pierre-Marc rather separately from the per-thread
> state machine. The appropriate way to integrate all this might have
> rather been to integrate both state machines together.

Yes.

> But in this case, it's a problem-specific state machine to detect a
> particular condition/pattern. What we're trying to find out here is
> if there is value in describing a state machine directly within the
> instrumentation metadata, so we can have a basic model that describes
> the traced system. If we think of the trace data as compressed at
> generation-time by only saving the state machine changes into the
> trace records, it makes sense to represent this state machine as part of
> the metadata to allow automatic "decompression" of the trace data.

Yes, the state updates should be described along with the tracepoints. It is not completely disconnected from the associated analysis modules since you may decide to model more things (e.g. file descriptor tables) is you have specific new analysis modules in mind.


Back to the top