Hey Nate,
yea, I would be looking for a variation of what your describing here.

Basically, I want to maybe do something like:
m5.debug configs/example/se.py --trace-all-objects -d --caches

So since this would be an O3 simulation, then that would mean I would
want all CPU flags, the TLB, the Cache, and also the Exec flag.

To do this, you would have to infer what flags are relevant to what
objects based on where the flags are defined. For instance: O3CPU
flags are defined in src/o3/SConscript, so I could infer all flags in
src/cpu/SConscript and all flags in src/cpu/o3/SConscript are
relevant.

I know this is an involved process potentially and maybe its just
something that would make life easier for me so we'll see what people
think about it.

nate,
if you did add the capability of adding trace-flags through the
configuration files then eventually I could get around to doing what I
described above.

On Fri, Apr 17, 2009 at 1:35 PM, nathan binkert <[email protected]> wrote:
>> I'm not sure what you mean.  You just make up a traceflag calle O3CPUAll, or
>> even KoreysO3Flags , you could make whatever you want, it won't affect
>> anyone.
>> See src/cpu/SConscript and look at the CompoundFlags - that's how Exec
>> works, it's a collection of lots of other flags.
>
> But committing KoreysO3Flags to the tree would be annoying.  You can
> turn on flags from the python, so you could just add an option to your
> script to turn on flags.  You could also use $HOME/.m5/options.py to
> modify the default set of flags.  I could add support for defining
> your own composite flags in something like $HOME/.m5/flags.py if
> people think that would be useful.  It would actually be rather easy
> to do.
>
>  Nate
> _______________________________________________
> 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

Reply via email to