diff options
author | Geoffrey Blake <geoffrey.blake@arm.com> | 2013-02-15 17:40:10 -0500 |
---|---|---|
committer | Geoffrey Blake <geoffrey.blake@arm.com> | 2013-02-15 17:40:10 -0500 |
commit | 8e79c68936f819e9efa05e5085232bd501af2bc7 (patch) | |
tree | 72ca6052724501e447b1d175cc8790f01f173e20 /src/dev/DiskImage.py | |
parent | 27630e9cad56d22f73408cfd72d453776c0f2a05 (diff) | |
download | gem5-8e79c68936f819e9efa05e5085232bd501af2bc7.tar.xz |
cpu: Fix rename mis-handling serializing instructions when resource constrained
The rename can mis-handle serializing instructions (i.e. strex) if it gets
into a resource constrained situation and the serializing instruction has
to be placed on the skid buffer to handle blocking. In this situation the
instruction informs the pipeline it is serializing and logs that the next
instruction must be serialized, but since we are blocking the pipeline
defers this action to place the serializing instruction and
incoming instructions into the skid buffer. When resuming from blocking,
rename will pull the serializing instruction from the skid buffer and
the current logic will see this as the "next" instruction that has to
be serialized and because of flags set on the serializing instruction,
it passes through the pipeline stage as normal and resets rename to
non-serializing. This causes instructions to follow the serializing inst
incorrectly and eventually leads to an error in the pipeline. To fix this
rename should check first if it has to block before checking for serializing
instructions.
Diffstat (limited to 'src/dev/DiskImage.py')
0 files changed, 0 insertions, 0 deletions