From: Philippe E. <ph...@cl...> - 2002-03-09 15:26:34
|
> TODO: > - demangling + all counter optionnally etc.. > - folderview of sample files + sessions in the gui itself see later. > - disassembly. form "+0x8b" for intra-symbol samples to match objdump output ? > - hotspot ... is this op_time ?? nope | | | | | | | | ------------------ vma axis (eg for /bin/ls) My plan was to build separate application for oprofpp and op_time and allow to launch one from the other: - from oprof_report a simple button "overall" - from oprof_overall double click on an item (an application) to launch oprof_report on this application > - source - source is a simple class to show file annotated, the code will be shared between the two application. oprof_report does not need to deal with session, you just select the right sub-dir in samples dir. I prefer make it in this way: more maintainable application and interface less confusing for user. I've not a clear view for now how to deal with op_diff. later oprof_report can add: - calculated field eg with branch retired, branch mispredicted events we allow user to add a column (#0 - #1) / #0 to see where it must look for branch that are too often mispredicted. *** Is the current design of oprof_report ok ? regards, Phil |
From: John L. <le...@mo...> - 2002-03-09 17:31:02
|
On Sat, Mar 09, 2002 at 03:50:56PM +0100, Philippe Elie wrote: > + all counter optionnally etc.. yep > > - disassembly. form "+0x8b" for intra-symbol samples > > to match objdump output ? yeah that would make sense > | > | | > | | > | | | > ------------------ vma axis (eg for /bin/ls) ah ok... I'm going to do some studies of how badly the page granularity pans out soon. > My plan was to build separate application for oprofpp and > op_time and allow to launch one from the other: > - from oprof_report a simple button "overall" > - from oprof_overall double click on an item (an application) > to launch oprof_report on this application hmm, and if I want to look at mutltiple profiles (by-eye op_diff) ? I'd really prefer them to be one app > oprof_report does not need to deal with session, you just select the > right sub-dir in samples dir. I prefer make it in this way: more > maintainable application and interface less confusing for user. but the file selector doesn't show the info they want. I want to see : session1/ (last modified bahl blah ...) and I can get tooltip/info to show me what options were used etc. > eg with branch retired, branch mispredicted events we allow user > to add a column (#0 - #1) / #0 to see where it must look for branch > that are too often mispredicted. sounds good. > Is the current design of oprof_report ok ? sure, but you've done the easiest bit. I know you don't believe that getting a really good oprof_report is hard :) I haven't looked at the source at all regards john |