As you may know, each ISA has a different memory consistency model and depending on the model, different information needs to be communicated between Ruby and the O3 LSQ. For example, a snooping load queue typically used by TSO would require Ruby to communicate snoops to the LSQ. Meanwhile, an insulated load queue needs to squash and restart loads that violate the consistency model.
As far as the store buffer goes, I believe there was an old thread about that. I seem to remember that we decided that the store buffer should live inside the CPU model, but I'm not sure. That will obvious have implications on the O3-Ruby interface as well. If you decide to pursue this, please use Reviewboard to keep us up-to-date with your progress. Thanks, Brad > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of huangyongbing > Sent: Wednesday, August 24, 2011 7:32 PM > To: [email protected] > Subject: [gem5-dev] The O3-Ruby interface is work in progress？ > > Hi， > > > > I want to use O3-Ruby model. So I need to know how long this > work > will be completed. Or, what should I do in order to implement it based > on > current O3 CPU and Ruby codes? > > > > To my knowledge, the memory requests are sent from LSQ in O3 CPU. > Besides > connecting LSQ port with Ruby port, what other works are included? > > > > Hope to be replied soon. Thanks. > > > > > > --Yongbing Huang > > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
