> > Instead of this, couldn't you do the cross thread thing by looking up > the appropriate thread context in the cpu object and then calling the > register access function for that thread context? This would work > more in line with the other CPU models. > I've been looking into this and it seems that the difference between the In-Order model and the O3 is that an instruction accesses the register file by directly calling the CPU object rather than through using the Thread Context.
I'm guessing if I re-adjust all InOrder code to make sure it uses the Thread Context to interface with a CPU's regfile then we would probably be back to full compatibility... The question I'm trying to figure out in my mind again is: what is the advantage of using the thread context to access the CPU instead of letting an instruction directly access it? What flexibility are we gaining? Currently, it just seems like an indirect step... ---------- Korey L Sewell Graduate Student - PhD Candidate Computer Science & Engineering University of Michigan
_______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
