Re: Advice about process-specific graphical view

Mathieu Desnoyers <[email protected]>
Newsgroups gmane.linux.kernel.tracing
Message-ID <20070622123039.GA2135@Krystal>
* CASTOR, Mikael ([email protected]) wrote:
> Hello,
> 
> About the post-processing, what I wanted to do is to simplify the
> control flow viewer. I mean, there are many process linked belonging
> to the OS. I wanted those process to be merged into one (for example
> make groups  by functions, process linked to graphical functions,
> other to basic kernel functions, ...). I don't know if my explnation
> is obvious.
> 
> Here is an example of use :
> 
> I create one process father, child process discussing each other and
> having kernel access (for example use of pipe to exchange
> informations).  Another process, with a high priority and using kernel
> signals (like sighup, ...).
> 
> So with that my goal is to see something like that :
> 
> P1 (father)  ________		    _________	     ____     ____ |	   |
> |		 |	    |    |   |	| __   ______		  ________			 ________ P2
> (child)		   |	| |	   |		 |	    |			|	   | ___ P3 (High priority
> process)					   |	 |
> 					
> Idle _ Kernel			| |
> 
> Graphical Interface
> 
> 
> Here is an example of what I wanted to have. If you know a best way to
> obtain that kind of results, I would be pleased to know.
> 

Sure, here is my suggestion:

Use the filter (either the global tab filter in the toolbar at the top,
or the filter at the left of the control flow view. use the expression:

state.target_pid=pidparent | state.target_pid=pidchild | state.target_pid=0

It should show only these processes.

If you want to add icons or symbols whenever events are encountered, you
will have to tweak the control flow view code to do that: currently, the
figure drawing primitives are there, but linked to no event. I plan to
eventually implement a control flow view "properties" box which would
allow users to specify mappings between events and icons or basic
geometric figures. Users could even provide their own icon set. I just
never had time to finish it. Help on this would be welcome :)

Regards,

Mathieu


> 
> PS : I heard about timedoctor, but I don't see how it can use traces
> from lttng (maybe a reformating is needed). I d'ont know if you
> already use it ?
> 
> 
> -----Message d'origine-----
> De : Mathieu Desnoyers [mailto:[email protected]]
> Envoyé : jeudi 21 juin 2007 20:52
> À : CASTOR, Mikael
> Objet : Re: Need some advice
> 
> 
> Hi Mikael,
> 
> * CASTOR, Mikael ([email protected]) wrote:
> > Hello,
> > 
> > LTTng : 0.6.8
> > OS : Mandriva One 2007.1 (KDE)
> > 
> > I need some "personnal" advice for, as you supose, an lttng issue.
> > First of all, I've got something strange on tracing system calls, LTTV
> > doesn't give me the name of the process started before the launching
> > of the different modules. Instead of having the name I've got
> > UNNAMEDfor processes, is it due to the fact I don't load
> > ltt-statedump? But it's still strange because user processes have
> > their correct name.
> > 
> 
> Processes running on the system are named at trace start, by
> ltt-statedump. Afterward, only newly created processes, issuing a exec()
> system, will have their name set.
> 
> 
> > Second thing, I wanted to copmpute some restriction on tracing
> > filtering and on post-processing filtering. What is the best way?  For
> > example I would lioke to have all  kernel (& OS) process merge into
> > one line and be able to see all the preemptions of the kernel from
> > processes with different priority level launched in userspace.
> > 
> 
> I am not sure I understand fully what you are trying to show. Can you
> explain a little more what you are trying to visualize ?
> 
> > Thaks, Best regards,
> > 
> > Mikaël Castor.
> > 
> > This e-mail is intended only for the above addressee. It may contain
> > privileged information.  If you are not the addressee you must not
> > copy, distribute, disclose or use any of the information in it.  If
> > you have received it in error please delete it and immediately notify
> > the sender.  Security Notice: all e-mail, sent to or from this
> > address, may be accessed by someone other than the recipient, for
> > system management and security reasons. This access is controlled
> > under Regulation of security reasons.  This access is controlled under
> > Regulation of Investigatory Powers Act 2000, Lawful Business
> > Practises.
> > 
> > 
> > 
> 
> -- 
> Mathieu Desnoyers
> Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
> 
> This mail has originated outside your organization, either from an external partner or the Global Internet.
> Keep this in mind if you answer this message.
> 
> 
> 
> This e-mail is intended only for the above addressee. It may contain privileged information.
> If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. 
> If you have received it in error please delete it and immediately notify the sender.
> Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of security reasons.
> This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises.
> 
> 
> 

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.