From: John L. <le...@mo...> - 2002-08-28 16:11:47
|
On Tue, Aug 27, 2002 at 11:59:37PM -0700, Ka Fai Lau wrote: > I have done a smiliar DCPI project in my school but I > was using RTC because I couldn't get APIC work. I > believe the DCPI idea is really cool and I am really > excited that oprofile get it started on Linux :D. > > I am interested to implement the TODO list item - > "thread profiling". Can someone give me some idea > about what is the direction and what should be > expected? Basically all that is needed (I believe) is a facility to split out the sample files by pid as well as binary name. This is partly tied in to the re-working we need to do of the user space stuff (see oprofile-tests/pp_interface in oprofile-tests cvs module), but we can also do this with the current code. Basically provide an option to the daemon to turn on thread profiling, then save out samples with a given pid (sample->pid) into separate file names. It shouldn't be too difficult. One question is whether we should restrict it to some set of processes, or whether we should just turn it on when requested for all processes (this would mean that 10 invocations of /bin/ls creates 10 sample files). Shout if you want some more detailed info. Phil, what's your thoughts ? regards john -- "When your name is Winner, that's it. You don't need a nickname." - Loser Lane |