Searched hist:6863 (Results 1 - 6 of 6) sorted by relevance

/gem5/src/mem/slicc/ast/
H A DPeekStatementAST.py6863:21fbf0412e0d Tue Jan 19 18:11:00 EST 2010 Derek Hower <drh5@cs.wisc.edu> ruby: new atomics implementation

This patch changes the way that Ruby handles atomic RMW instructions. This implementation, unlike the prior one, is protocol independent. It works by locking an address from the sequencer immediately after the read portion of an RMW completes. When that address is locked, the coherence controller will only satisfy requests coming from one port (e.g., the mandatory queue) and will ignore all others. After the write portion completed, the line is unlocked. This should also work with multi-line atomics, as long as the blocks are always acquired in the same order.
/gem5/src/mem/slicc/
H A Dparser.py6863:21fbf0412e0d Tue Jan 19 18:11:00 EST 2010 Derek Hower <drh5@cs.wisc.edu> ruby: new atomics implementation

This patch changes the way that Ruby handles atomic RMW instructions. This implementation, unlike the prior one, is protocol independent. It works by locking an address from the sequencer immediately after the read portion of an RMW completes. When that address is locked, the coherence controller will only satisfy requests coming from one port (e.g., the mandatory queue) and will ignore all others. After the write portion completed, the line is unlocked. This should also work with multi-line atomics, as long as the blocks are always acquired in the same order.
/gem5/src/mem/ruby/slicc_interface/
H A DAbstractController.hh6863:21fbf0412e0d Tue Jan 19 18:11:00 EST 2010 Derek Hower <drh5@cs.wisc.edu> ruby: new atomics implementation

This patch changes the way that Ruby handles atomic RMW instructions. This implementation, unlike the prior one, is protocol independent. It works by locking an address from the sequencer immediately after the read portion of an RMW completes. When that address is locked, the coherence controller will only satisfy requests coming from one port (e.g., the mandatory queue) and will ignore all others. After the write portion completed, the line is unlocked. This should also work with multi-line atomics, as long as the blocks are always acquired in the same order.
/gem5/src/mem/ruby/system/
H A DSequencer.hh6863:21fbf0412e0d Tue Jan 19 18:11:00 EST 2010 Derek Hower <drh5@cs.wisc.edu> ruby: new atomics implementation

This patch changes the way that Ruby handles atomic RMW instructions. This implementation, unlike the prior one, is protocol independent. It works by locking an address from the sequencer immediately after the read portion of an RMW completes. When that address is locked, the coherence controller will only satisfy requests coming from one port (e.g., the mandatory queue) and will ignore all others. After the write portion completed, the line is unlocked. This should also work with multi-line atomics, as long as the blocks are always acquired in the same order.
H A DSequencer.cc6863:21fbf0412e0d Tue Jan 19 18:11:00 EST 2010 Derek Hower <drh5@cs.wisc.edu> ruby: new atomics implementation

This patch changes the way that Ruby handles atomic RMW instructions. This implementation, unlike the prior one, is protocol independent. It works by locking an address from the sequencer immediately after the read portion of an RMW completes. When that address is locked, the coherence controller will only satisfy requests coming from one port (e.g., the mandatory queue) and will ignore all others. After the write portion completed, the line is unlocked. This should also work with multi-line atomics, as long as the blocks are always acquired in the same order.
/gem5/src/mem/slicc/symbols/
H A DStateMachine.py6863:21fbf0412e0d Tue Jan 19 18:11:00 EST 2010 Derek Hower <drh5@cs.wisc.edu> ruby: new atomics implementation

This patch changes the way that Ruby handles atomic RMW instructions. This implementation, unlike the prior one, is protocol independent. It works by locking an address from the sequencer immediately after the read portion of an RMW completes. When that address is locked, the coherence controller will only satisfy requests coming from one port (e.g., the mandatory queue) and will ignore all others. After the write portion completed, the line is unlocked. This should also work with multi-line atomics, as long as the blocks are always acquired in the same order.

Completed in 54 milliseconds