Yea, at some point it becomes subjective (and dependent on the specific problem you're tracking down) to say what's "related". If "O3CPUAll" isn't sufficient, what is there in "All" that is too much noise to deal with? Basically the only thing in All that I find truly annoying is the Event stuff, so if I'm not tracing something specific like Cache or Bus I usually find that "All,-Event" is pretty good.
Steve On Fri, Apr 17, 2009 at 8:59 AM, Korey Sewell <[email protected]> wrote: > Sure I cooouuuld, but something tells me adding Exec, TLB, Cache, etc. > etc. would not be met with open-arms since technically I'm merging > different object flags together BUT all these different objects are > related to each other. > > I guess I want a per-configuration relevant trace flag listing so > nothing slips under the cracks when I'm trying to debug something. > Maybe that's specific to how I want to use M5 so I could see why > people think the "*All" Flags are sufficient. > > On Fri, Apr 17, 2009 at 11:50 AM, Lisa Hsu <[email protected]> wrote: > > You could just cobble everything you want together into a composite flag > and > > call it O3CPUAll.....then not only would it be easy to see but easy to > turn > > on. > > On Fri, Apr 17, 2009 at 11:47 AM, Korey Sewell <[email protected]> > wrote: > >> > >> Yea, that's helpful. I guess I am looking for a more fine-grained > >> control of things in terms of "show me all flags that have to do with > >> me running O3CPU". > >> > >> You would think "O3CPUAll" would be enough, but there are some base > >> flags that are relevant (e.g. TLB or Cache) that I would want to > >> include. > >> > >> I could understand if most people thought the functionality present is > >> enough though... > >> > >> On Fri, Apr 17, 2009 at 9:32 AM, Lisa Hsu <[email protected]> wrote: > >> > m5.opt --trace-help > >> > that will list all available trace flags, including composite ones. > >> > m5.opt > >> > -h will give a big usage blurb too, so that you can see if you want is > >> > available. > >> > Lisa > >> > > >> > On Fri, Apr 17, 2009 at 2:56 AM, Korey Sewell <[email protected]> > wrote: > >> >> > >> >> I'm wondering if anybody would find this useful or not. > >> >> > >> >> Basically, when debugging, I often find myself going through > >> >> SConscript files trying to remember or find out what trace-flag is > >> >> available for a particular object. > >> >> > >> >> For instance, just now, I wanted to view the Exec trace but didnt > want > >> >> the symbols. And a little earlier, I wanted to figure out if I could > >> >> just print out the branch prediction info but none of the other > >> >> information. > >> >> > >> >> So it's slightly annoying for me to have to do that all the time. > >> >> > >> >> One solution might for me to just remember all the trace flags for > >> >> things I care about :) > >> >> > >> >> But it might be nice to novice and expert users if you could view > >> >> trace-flags for a particular object or set of objects from the > command > >> >> line. > >> >> > >> >> I imagine I want something like: ./m5.debug --view-flags=O3CPU > >> >> > >> >> So does anybody else think that would be a useful thing? > >> >> > >> >> -- > >> >> ---------- > >> >> Korey L Sewell > >> >> Graduate Student - PhD Candidate > >> >> Computer Science & Engineering > >> >> University of Michigan > >> >> _______________________________________________ > >> >> m5-dev mailing list > >> >> [email protected] > >> >> http://m5sim.org/mailman/listinfo/m5-dev > >> >> > >> > > >> > > >> > _______________________________________________ > >> > m5-dev mailing list > >> > [email protected] > >> > http://m5sim.org/mailman/listinfo/m5-dev > >> > > >> > > >> > >> > >> > >> -- > >> ---------- > >> Korey L Sewell > >> Graduate Student - PhD Candidate > >> Computer Science & Engineering > >> University of Michigan > >> _______________________________________________ > >> m5-dev mailing list > >> [email protected] > >> http://m5sim.org/mailman/listinfo/m5-dev > >> > > > > > > _______________________________________________ > > m5-dev mailing list > > [email protected] > > http://m5sim.org/mailman/listinfo/m5-dev > > > > > > > > -- > ---------- > Korey L Sewell > Graduate Student - PhD Candidate > Computer Science & Engineering > University of Michigan > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev >
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
