so base_dyn_inst is always used timing memory - I assumed so but just wanted to confirm this to make sure that read function,
BaseDynInst<Impl>::read(Addr addr, T &data, unsigned flags) 'data' argument isn't really doing anything but being a placeholder for func sig matching in xc interface. -- is this correct? BaseDynInst::read() will be called only in initiateAcc(), not in execute() function. When the initiateAcc()/completeAcc() pair is used, pkt->get() is used in completeAcc() to read the data. I am moving some code from read() to finishTranslation() and it looks like 'data' variable doesn't need to be passed. Thanks, Min On Thu, Jul 15, 2010 at 10:01 AM, Steve Reinhardt <ste...@gmail.com> wrote: > On Wed, Jul 14, 2010 at 8:35 AM, Min Kyu Jeong <mkje...@gmail.com> wrote: > > b) memory is atomic (is it a possible combination? dyn_inst + atomic?) - > > x86 doesn't seem to have code for this case - Walker::recvAtomic() does > > nothing. > > I don't believe that O3+atomic mode works. Practically speaking it > doesn't make any sense. > > Steve > _______________________________________________ > m5-dev mailing list > m5-dev@m5sim.org > http://m5sim.org/mailman/listinfo/m5-dev >
_______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev