I'm confused. Korey, I thought this DMA problem only existed with Ruby? If so, how were you able to reproduce it using atomic mode? Ruby does not work with the atomic cpu model.
Please clarify, thanks! Brad > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Korey Sewell > Sent: Tuesday, March 15, 2011 12:09 PM > To: M5 Developer List > Subject: Re: [m5-dev] Ruby FS - DMA Controller problem? > > Hi Brad/Malek, > I've been able to regenerate this error in about 20mins now (instead of > hours) by running things in atomic mode. Not sure if that helps or not... > > On Tue, Mar 15, 2011 at 3:03 PM, Beckmann, Brad > <[email protected]>wrote: > > > > How is that you are able to run the memtester in FS Mode? > > > I see the ruby_mem_tester.py in /configs/example/ but it seems that > > > it is only configured for SE Mode as far as Ruby is concerned? > > > > I don't run it in FS mode. Since the DMA bug manifests only after > > hours of execution, I wanted to first verify that the DMA protocol > > support was solid using the mem tester. Somewhat surprisingly, I > > found several bugs in MOESI_CMP_directory's support of DMA. It turns > > out that the initial DMA support in that protocol wasn't very well > > thought out. Now I fixed those bugs, but since the DMA problem also > > arises with the MOESI_hammer protocol, I'm confident that my patches > don't fix the real problem. > > > > Brad > > > > _______________________________________________ > > m5-dev mailing list > > [email protected] > > http://m5sim.org/mailman/listinfo/m5-dev > > > > > > -- > - Korey > _______________________________________________ > 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
