summaryrefslogtreecommitdiff
path: root/SConstruct
diff options
context:
space:
mode:
authorAndreas Sandberg <Andreas.Sandberg@ARM.com>2013-01-07 13:05:37 -0500
committerAndreas Sandberg <Andreas.Sandberg@ARM.com>2013-01-07 13:05:37 -0500
commit63f1d0516d8a4e5a688cc3000b5a3597518d3dc7 (patch)
treea1a33ec62895dd6f8fa2de234a6186112e33b40c /SConstruct
parentfffdc6a45019639cd8f899fa81eeb732db3e6f8c (diff)
downloadgem5-63f1d0516d8a4e5a688cc3000b5a3597518d3dc7.tar.xz
arm: Fix DMA event handling bug in the PL111 model
The PL111 model currently maintains a list of pre-allocated DmaDoneEvents to prevent unnecessary heap allocations. This list effectively works like a stack where the top element is the latest scheduled event. When an event triggers, the top pointer is moved down the stack. This obviously breaks since events usually retire from the bottom (events don't necessarily have to retire in order), which triggers the following assertion: gem5.debug: build/ARM/dev/arm/pl111.cc:460: void Pl111::fillFifo(): \ Assertion `!dmaDoneEvent[dmaPendingNum-1].scheduled()' failed. This changeset adds a vector listing the currently unused events. This vector acts like a stack where the an element is popped off the stack when a new event is needed an pushed on the stack when they trigger.
Diffstat (limited to 'SConstruct')
0 files changed, 0 insertions, 0 deletions