Two things: 1) I see that there is an instruction flag in the Request Objects called "INST_FETCH" but I didnt see anywhere in the code where this is being utilized... Are there plans to use this information for maybe like cache replacement policies or ???
2) I just updated the inorder code to fetch instructions at cache block granularity (64 bytes) instead of instruction granularity (8 bytes). The O3CPU already does this. I was wondering if the SimpleCPUs wouldnt also really benefit from this considering if you can avoid making calls to the memory system for maybe 5 out of every 8 instructions thats a nice little performance boost. The setupFetchRequest code in base.cc forms a request for the size of the instruction instead of the cache block: " req->setVirt(0, fetchPC, sizeof(MachInst), Request::INST_FETCH, threadPC);" Does anyone have any thoughts on this on why this may or may not be a good thing? -- - Korey _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
