Re: [gem5-dev] Review Request 2549: ruby: ruby port: do not check for blocked ports

2015-02-10 Thread Joel Hestness via gem5-dev
Bump. I was finally able to update to a more recent version of gem5, and I immediately ran into this problem when trying to run a simple test with x86 O3CPU and Ruby. Here's the assertion failure again: gem5.opt: build/X86/mem/ruby/system/RubyPort.hh:190: void RubyPort::addToRetryList(RubyPort:

Re: [gem5-dev] Review Request 2636: mem: fix prefetcher bug regarding write buffer hits

2015-02-10 Thread Steve Reinhardt via gem5-dev
> On Feb. 10, 2015, 9:37 a.m., Stephan Diestelhorst wrote: > > I have had a similar impulse, when inspecting this code. However, the > > prefetch hitting a write-back in an upper cache is actually already handled > > in Cache::getTimingPacket(): > > > > // Check if the prefetch hi

Re: [gem5-dev] Review Request 2636: mem: fix prefetcher bug regarding write buffer hits

2015-02-10 Thread Steve Reinhardt via gem5-dev
> On Feb. 10, 2015, 9:37 a.m., Stephan Diestelhorst wrote: > > I have had a similar impulse, when inspecting this code. However, the > > prefetch hitting a write-back in an upper cache is actually already handled > > in Cache::getTimingPacket(): > > > > // Check if the prefetch hi

Re: [gem5-dev] Issue with O3 and interrupts

2015-02-10 Thread Joel Hestness via gem5-dev
Hey Gabe and Nilay, Have either of you had a chance to look into this more deeply? I'm running into what appears to be the same problem: The CPU core pulls the interrupt from the interrupts device (by calling getInterrupt() and then updateIntrInfo()). Then, while fetching/decoding the first in

Re: [gem5-dev] Review Request 2647: cpu: o3 register renaming request handling improved

2015-02-10 Thread Andreas Hansson via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2647/ --- (Updated Feb. 10, 2015, 5:43 p.m.) Review request for Default. Repository: gem5

Re: [gem5-dev] Review Request 2636: mem: fix prefetcher bug regarding write buffer hits

2015-02-10 Thread Stephan Diestelhorst via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2636/#review5885 --- I have had a similar impulse, when inspecting this code. However, the pr

Re: [gem5-dev] Review Request 2627: Ruby: Update backing store option to propagate through to all RubyPorts

2015-02-10 Thread Jason Power via gem5-dev
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2627/ --- (Updated Feb. 10, 2015, 4:02 p.m.) Review request for Default. Changes --- D

Re: [gem5-dev] changeset in gem5: ruby: dma sequencer: remove RubyPort as paren...

2015-02-10 Thread Jason Power via gem5-dev
Hey Brad, It may not solve the multi-cache block problem, but it does get us closer to a working backing store ;). Do you see a simple change to this patch to get multi-cache block DMA working? I don't have a program to test this with, so I'm not sure if I'm the right person to do it. Does it mak

Re: [gem5-dev] changeset in gem5: ruby: dma sequencer: remove RubyPort as paren...

2015-02-10 Thread Andreas Hansson via gem5-dev
Hi all, To me it sounds like the whole ruby philosophy of “two, or even three views of the same data” might need an overhaul. Andreas On 10/02/2015 04:44, "Beckmann, Brad via gem5-dev" wrote: >Thanks Jason. I didn't notice your patch until after I sent out my >email. It looks like we are enc

[gem5-dev] Cron /z/m5/regression/do-regression quick

2015-02-10 Thread Cron Daemon via gem5-dev
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/minor-timing passed. * build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/o3-timing passed. * build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple-atomic passed. * build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple