It would probably need to be a global function which took a thread context (exec context?) as a parameter since the information can vary by CPU, but I think that could work.
Gabe Steve Reinhardt wrote: > Collecting the necessary information in Python up front seems > reasonable to me. > > As far as where the C++ code would go, it seems to me it could either > be a method on the BaseCPU object or a global function in the x86 ISA > namespace. The latter makes sense if we're trying not to pollute the > CPU model with a lot of ISA-specific stuff. I don't see the advantage > of making the ISA a SimObject instead of a namespace unless we want to > do something like make it a template parameter of the CPU objects (to > enable heterogeneous ISA support). > > Steve > > ------------------------------------------------------------------------ > > _______________________________________________ > 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
