@wiki 56582 2008-05-03T03:07:52Z @wiki::25/ 2008-04-03 2008-05-03T03:07:52Z

Boot Notes 0xff f000 0000 +0x0 reset +0x20

@wiki::24/ 2007-11-18 2008-04-01T22:58:12Z

GNU Assembler from Binutils 2.18 the assembler has been updated to support the extended SPARC ISA file modified is opcodes/sparc-opc.c configured for the sparc-sun-solaris target

@wiki::23/ 2007-11-18 2007-11-18T02:24:54Z

GNU Assembler from Binutils 2.18 -the assembler has been updated to support the extended SPARC ISA -file modified is opcodes/sparc-opc.c -configured for the sparc-sun-solaris target

@wiki::22/ 2007-11-01 2007-11-01T15:55:39Z

ugekjsdjkf

@wiki::21/ 2007-11-01 2008-05-03T06:09:04Z

Name   Bits Desc File Checkpoint Rollback Commit bw_r_frf ASR0 64 wide 128 entries Floating Point register File  bw_r_frf.v                      

@wiki::20/ 2007-11-01 2007-11-01T05:41:15Z

     

@wiki::19/ 2007-11-01 2007-11-01T04:05:56Z

    This cache implements the write-back policy. A new “Speculative” state is added to each line. This allows the cache to differentiate cache blocks that was written after a checkpoint was taken. If a speculative block has to be evicted, the corresponding block in the next lower hierarchy will be marked as “Speculative”.     However if the following level is the main memory or a normal cache, then the checkpoint will be discarded and all blocks in “Speculative” state will be changed to “Dirty”. This effectively commits all operations after a checkpoint. On the event of a rollback, every speculative cache block will be invalidated.     The proposed design allows quick checkpoint taking. On the other hand, rolling back or committing a checkpoint is very expensive because a full traversal of the cache is needed.

@wiki::18/ 2007-11-01 2008-04-18T03:17:37Z

    Write history queue is used to save the data in memory that is overwritten by post-checkpoint store operations. After a checkpoint is taken, every subsequent store operation will cause the old data and its memory address to be stored in the write history queue. The WHQ will ignore further writes to the same address as we are only concern with the original value to perform a rollback.          When a checkpoint is committed, the data and address stored in the write history queue will be dumped. However, on the event of a rollback, the data in the queue will be written back into the memory at the corresponding addresses. In addition, all caches in the higher hierarchy have to be flushed.     This design allows quick checkpoint taking and checkpoint committing. However, it has a terrible rollback performance and might be slower during speculative mode compared to the other methods since it allows writes to the main memory.

@wiki::17/ 2007-11-01 2007-11-01T04:05:16Z

    A gated store buffer is a component that temporarily holds all memory stores generated after the checkpoint. In speculative mode, it acts as a storage location to hold both the address and data for a memory store operation. Newer stores to the same address will overwrite the old data in the buffer.     After the buffer is filled up, the checkpoint has to be committed and data in the buffer will be transferred sequentially to the memory. The GSB can instantly roll back to the previous memory state by discarding the stored data and disabling the GSB.     This implementation allows quick checkpoint taking and rolling back. However checkpoint committing is expensive because all the data in the buffer need to be written into the memory. We could possibly pipeline the write-back operation so that the processor could resume normal execution earlier.

@wiki::16/ 2007-11-01 2007-11-01T05:38:55Z

Department of Electrical and Computer Engineering Carnegie Mellon University   Students Teck Hua Lee: teckl AT ece.cmu.edu Tze Chang Ng: tcng AT ece.cmu.edu Wei Jie Lee: weilee AT ece.cmu.edu   Advisor Prof. James Hoe: jhoe AT ece.cmu.edu   Credits Jared Smolens - OpenSPARC development and simulation setup Fall 2007 18-741 course staff - Feedback for the transactional memory evaluation class project