<message below> Why did it work before the block size patch? > - When the ChuckGenerator sees the block size is 0, it doesn't split up the > request into multiple patches and sends the whole dma request at once. That > is fine because the DMASequencer splits the request into multiple requests > and only responds to the dma port when the entire request is complete. > With regards to the old changeset that boots with the block size = 0, I was not able to boot a large scale CMP system (more than 16 cores) due to the "deadlock threshold" being triggered.
I'm assuming that Brad has a read on how to fix that problem so I'll probably start working on what is causing that deadlock so hopefully we can kind of pipeline the bug fixes. -- - Korey _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
