On 14-02-20 10:52 AM, Geneviève Bastien wrote:
>
>
> * The LTTng UST Memory usage analysis is a more tricky (and
> interesting!) case: It has events. Adding the context TID and procname
> will give a more interesting analysis, but the analysis can still do
> something without it.
That's interestin
>>
>> Some questions:
>> - A "string" requirement is quite generic. What actual types of
>> requirements do you have in mind? I can see event type (or event name),
>> but what else? If we can pinpoint a few specific types of requirements,
>> we could have a couple of methods specifically for those
Hi Guilliano,
Thanks! I'll add your contribution so far on gerrit to be able to better
appreciate it and review it.
On 02/20/2014 10:11 AM, Guilliano Molaire wrote:
Hi Alex,
On 19/02/2014 4:45 PM, Alexandre Montplaisir wrote:
Hi Guilliano,
Interesting project! Indeed, there is already an A
Hi Alex,
On 19/02/2014 4:45 PM, Alexandre Montplaisir wrote:
Hi Guilliano,
Interesting project! Indeed, there is already an API for traces to
indicate if they contain specific events (hasEvent(String),
hasAllEvents(String[]),...).[1] The next step would be to have a way
for an analysis to spec
Hi Guilliano,
Interesting project! Indeed, there is already an API for traces to
indicate if they contain specific events (hasEvent(String),
hasAllEvents(String[]),...).[1] The next step would be to have a way
for an analysis to specify which event types they need, so we can match
the traces and
Hi everyone,
Mathieu Rail and I, Guilliano Molaire, are working on the TMF part of
linuxtools. Our main goal
is to provide an API for the analysis modules that will permit queries
of their requirements.
A requirement is basically a string container of his type (e.g.
"event_name") and all the
