EECC722 - Shaaban #1 lec # 10 Fall Thread Level Speculation (TLS) in the Stanford Hydra Chip Multiprocessor (CMP) A Chip Multiprocessor (CMP) based microarchitecture/compiler effort at Stanford that provides hardware/software support for Data/Thread Level Speculation (TLS) to extract parallel speculated threads from sequential code (single thread) augmented with software thread speculation handlers (Primary papers: 4, 6)

EECC722 - Shaaban #2 lec # 10 Fall Motivation for Chip Multiprocessors (CMPs) A CMP offers implementation benefits –High-speed signals are localized in individual CPUs –A proven CPU design may be replicated across the die (including SMT processors, e.g IBM Power 5) Overcomes diminishing performance/transistor return problem in uniprocessors (similar motivation for SMT) –Transistors are used today mostly for ILP extraction –MPs use transistors to run multiple threads... On parallelized programs With multiprogrammed workloads Fast inter-processor communication eases parallelization of code (Shared L2 cache)

EECC722 - Shaaban #3 lec # 10 Fall Stanford Hydra CMP Approach Goals Exploit all levels of program parallelism. Develop a single-chip multiprocessor architecture that simplifies microprocessor design and achieves high performance. Make the multiprocessor transparent to the average user. Integrate use of parallelizing compiler technology in the design of microarchitecture that supports data/thread level speculation (TLS). Within a single CPU core On multiple CPU cores within a single CMP or multiple CMPs On multiple CPU cores within a single CMP using Thread Level Speculation (TLS)

EECC722 - Shaaban #4 lec # 10 Fall The Basic Hydra CMP 4 processors and secondary cache on a chip 2 buses connect processors and memory Coherence: writes are broadcast on write bus

EECC722 - Shaaban #5 lec # 10 Fall Hydra Memory Hierarchy Characteristics

EECC722 - Shaaban #6 lec # 10 Fall CMP Parallel Performance Varying levels of performance –Multiprogrammed workloads work well –Very parallel apps (matrix-based FP and multimedia) are excellent –Acceptable only with a few less parallel (i.e. integer) applications Without Thread Level Speculation (TLS)

EECC722 - Shaaban #7 lec # 10 Fall The Parallelization Problem Current automated parallelization software (parallel compilers) is limited –Parallel compilers are generally successful for scientific applications with statically known dependencies (e.g dense matrix computations). –Automated parallization of general-purpose applications provides poor parallel performance especially for integer applications due to ambiguous dependencies resulting from: Significant pointer use: Pointer aliasing (Pointer disambiguation problem) Dynamic loop limits Complex control flow Irregular array accesses Inter-procedural dependencies –Ambiguous dependencies limit extracted parallelism/performance: Complicate static dependency analysis Introduce imprecision into dependence relations Force conservative performance-degrading synchronization to safely handle potential dependencies. Parallelism may exist in algorithm, but code hides it. Manual parallelization can provide good performance on a much wider range of applications: –Requires different initial program design/data structures/algorithms –Programmers with additional skills. – Handling ambiguous dependencies present in general-purpose applications may still force conservative synchronization greatly limiting parallel performance Can hardware help the situation?

EECC722 - Shaaban #8 lec # 10 Fall Possible Limited Parallel Software Solution: Data Speculation & Thread Level Speculation (TLS) Data speculation and Thread Level Speculation (TLS) enable parallelization without regard for data dependencies –Normal sequential program is broken up into speculative threads –Speculative threads are now run in parallel on multiple physical CPUs (e.g. CMP) and/or logical CPUs (e.g. SMT). –Speculation hardware (TLS processor) architecture ensures correctness Parallel software implications –Loop parallelization is now easily automated –Ambiguous dependencies resolved dynamically without conservative synchronization –More “arbitrary” threads are possible (subroutines) –Add synchronization only for performance Thread Level Speculation (TLS) hardware support mechanisms –Speculative thread control mechanism –Five basic speculation hardware/memory system requirements for correct data/thread speculation

EECC722 - Shaaban #9 lec # 10 Fall Subroutine Thread Speculation Speculated Thread

EECC722 - Shaaban #10 lec # 10 Fall Loop Iteration Speculative Threads A Simple example of a speculatively executed loop using Data/Thread Level Speculation (TLS) Original Sequential (Single Thread) Loop Speculated Threads Most common Application of TLS

EECC722 - Shaaban #11 lec # 10 Fall Overview of Loop-Iteration Thread Speculation Parallel regions (loop iterations) are annotated by the compiler. The hardware uses these annotations to run loop iterations in parallel as speculated threads on a number of CPUs. Each CPU knows which loop iteration it is running CPUs dynamically prevent data dependency violations –“later” iterations can’t use data before write by “earlier” iterations (RAW) –“earlier” iterations never see writes by “later” iterations (WAW): Multiple views of memory are created by TLS hardware If a “later” iteration has used data that an “earlier” iteration writes (RAW hazard), it is restarted –All following iterations are halted and restarted, also –All writes by the later iteration are discarded (undo speculated work).

EECC722 - Shaaban #12 lec # 10 Fall Hydra’s Data & Thread Speculation Operations

EECC722 - Shaaban #13 lec # 10 Fall Hydra Loop Compiling for Speculation

EECC722 - Shaaban #14 lec # 10 Fall Loop Execution with Thread Speculation

EECC722 - Shaaban #15 lec # 10 Fall Speculative Thread Creation in Hydra Register Passing Buffer (RPB)

EECC722 - Shaaban #16 lec # 10 Fall Speculative Data Access in Speculated Threads i Less Speculated thread i+1 More speculated thread WAR RAW WAW

EECC722 - Shaaban #17 lec # 10 Fall To provide the desired memory behavior, the data/thread speculation hardware must provide: 1. A method for detecting true memory dependencies, in order to determine when a dependency has been violated (RAW harard). 2. A method for backing up and re-executing speculative loads and any instructions that may be dependent upon them when the load causes a violation. 3. A method for buffering any data written during a speculative region of a program so that it may be discarded when a violation occurs or permanently committed at the right time. Speculative Data Access in Speculated Threads

EECC722 - Shaaban #18 lec # 10 Fall Five Basic Speculation Hardware Requirements For Correct Data/Thread Speculation 1. Forward data between parallel threads (RAW). A speculative system must be able to forward shared data quickly and efficiently from an earlier thread running on one processor to a later thread running on another. 2. Detect when reads occur too early (RAW hazards). If a data value is read by a later thread and subsequently written by an earlier thread, the hardware must notice that the read retrieved incorrect data since a true dependence violation has occurred. 3. Safely discard speculative state after violations. All speculative changes to the machine state must be discarded after a violation, while no permanent machine state may be lost in the process. 4. Retire speculative writes in the correct order (WAW hazards). Once speculative threads have completed successfully, their state must be added to the permanent state of the machine in the correct program order, considering the original sequencing of the threads. 5. Provide memory renaming (WAR hazards). The speculative hardware must ensure that the older thread cannot “see” any changes made by later threads, as these would not have occurred yet in the original sequential program. (i.g. Multiple views of memory)

EECC722 - Shaaban #19 lec # 10 Fall Speculative Hardware/Memory Requirements 1-2 (RAW) (RAW hazard or violation) 1 2 More Speculated Thread

EECC722 - Shaaban #20 lec # 10 Fall Speculative Hardware/Memory Requirements 3-4 (RAW hazard). (WAW hazards). Restart 3 4 More Speculated Thread

EECC722 - Shaaban #21 lec # 10 Fall Speculative Hardware/Memory Requirement 5 Memory Renaming to prevent WAR hazards. Write X by i+1 not visible to less speculated threads (thread i here) (i.e. no WAR hazard) Less speculated thread More Speculated Thread Even more Speculated Thread Not visible to less speculated thread i

EECC722 - Shaaban #22 lec # 10 Fall Hydra Thread Level Speculation (TLS) Hardware

EECC722 - Shaaban #23 lec # 10 Fall Hydra Thread Level Speculation (TLS) Support

EECC722 - Shaaban #24 lec # 10 Fall L1 Cache Tag Details - Record writes of more speculated threads

EECC722 - Shaaban #25 lec # 10 Fall L2 Speculation Buffer Details

EECC722 - Shaaban #26 lec # 10 Fall The Operation of Speculative Loads Check First Check Last Do Not Check: More Speculated Later writes not visible (otherwise WAR)

EECC722 - Shaaban #27 lec # 10 Fall Reading L2 Cache Speculative Buffers

EECC722 - Shaaban #28 lec # 10 Fall The Operation of Speculative Stores Less Speculated More Speculated Similar to invalidate cache coherency protocols

EECC722 - Shaaban #29 lec # 10 Fall Hydra’s Handling of Five Basic Speculation Hardware Requirements For Correct Data/Thread Speculation 1. Forward data between parallel threads (RAW). –When a speculative thread writes data over the write bus, all more-speculative threads that may need the data have their current copy of that cache line invalidated. –This is similar to the way the system works during non- speculative operation (invalidate cache coherency protocol). –If any of the threads subsequently need the new speculative data forwarded to them, they will miss in their primary cache and access the secondary cache. The speculative data contained in the write buffers of the current or older threads replaces data returned from the secondary cache on a byte-by-byte basis just before the composite line is returned to the processor and primary cache.

EECC722 - Shaaban #30 lec # 10 Fall Detect when reads occur too early (RAW hazards). –Primary cache bits are set to mark any reads that may cause violations. –Subsequently, if a write to that address from an earlier thread (less speculated) invalidates the address, a violation is detected, and the thread is restarted. 3. Safely discard speculative state after violations. –Since all permanent machine state in Hydra is always maintained within the secondary cache, anything in the primary caches and secondary cache speculation buffers may be invalidated at any time without risking a loss of permanent state. As a result, any lines in the primary cache containing speculative data (marked with a special modified bit) may simply be invalidated all at once to clear any speculative state from a primary cache. In parallel with this operation, the secondary cache buffer for the thread may be emptied to discard any speculative data written by the thread. Hydra’s Handling of Five Basic Speculation Hardware Requirements For Correct Data/Thread Speculation

EECC722 - Shaaban #31 lec # 10 Fall Retire speculative writes in the correct order (WAW hazards). –Separate secondary cache speculation buffers are maintained for each thread. As long as these are drained into the secondary cache in the original program sequence of the threads, they will reorder speculative memory references correctly. 5. Provide memory renaming (WAR hazards). –Each processor can only read data written by itself or earlier threads (less speculated threads) when reading its own primary cache or the secondary cache speculation buffers. –Writes from later threads don’t cause immediate invalidations in the primary cache, since these writes should not be visible to earlier (less speculative) threads. –However, these “ignored” invalidations are recorded using an additional pre- invalidate primary cache bit associated with each line. This is because they must be processed before a different speculative or non-speculative thread executes on this processor. –If future threads have written to a particular line in the primary cache, the pre- invalidate bit for that line is set. When the current thread completes, these bits allow the processor to quickly simulate the effect of all stored invalidations caused by all writes from later processors all at once, before a new thread begins execution on this processor. Hydra’s Handling of Five Basic Speculation Hardware Requirements For Correct Data/Thread Speculation

EECC722 - Shaaban #32 lec # 10 Fall Thread Speculation Performance Results representative of entire uniprocessor applications Simulated with accurate modeling of Hydra’s memory and hardware speculation support.

EECC722 - Shaaban #33 lec # 10 Fall Hydra Prototype Overview CPU core and cache. Speculative coprocessor –Speculative memory reference controller –Speculative interrupt screening mechanism –Statistics mechanisms for performance evaluation and to allow feedback for code tuning Memory system –Read and write buses –Controllers for all resources –On-chip L2 cache –Simple off-chip main memory controller –I/O and debugging interface

EECC722 - Shaaban #34 lec # 10 Fall Hydra Prototype Layout 250 MHz clock rate target

EECC722 - Shaaban #35 lec # 10 Fall Hydra Conclusions Hydra offers a number of advantages –Good performance on parallel applications –Promising performance on difficult to parallelize sequential (single-threaded) applications using data/Thread Level Speculation (TLS) mechanisms. –Scalable, modular design –Low hardware overhead support for speculative thread parallelism, yet greatly increases the number of parallel applications.

EECC722 - Shaaban #36 lec # 10 Fall Other Thread Level Speculation (TLS) Efforts: Wisconsin Multiscalar This CMP-based design proposed the first reasonable hardware to implement TLS. Unlike Hydra, Multiscalar implements a ring-like network between all of the processors to allow direct register-to-register communication. –Along with hardware-based thread sequencing, this type of communication allows much smaller threads to be exploited at the expense of more complex processor cores. The designers proposed two different speculative memory systems to support the Multiscalar core. –The first was a unified primary cache, or address resolution buffer (ARB). Unfortunately, the ARB has most of the complexity of Hydra’s secondary cache buffers at the primary cache level, making it difficult to implement. –Later, they proposed the speculative versioning cache (SVC). The SVC uses write-back primary caches to buffer speculative writes in the primary caches, using a sophisticated coherence scheme.

EECC722 - Shaaban #37 lec # 10 Fall This CMP-with-TLS proposal is very similar to Hydra, –Including the use of software speculation handlers. However, the hardware is simpler than Hydra’s. The design uses write-back primary caches to buffer writes— similar to those in the SVC—and sophisticated compiler technology to explicitly mark all memory references that require forwarding to another speculative thread. Their simplified SVC must drain its speculative contents as each thread completes, unfortunately resulting in heavy bursts of bus activity. Other Thread Level Speculation (TLS) Efforts: Carnegie-Mellon Stampede

EECC722 - Shaaban #38 lec # 10 Fall This CMP design has three processors that share a primary cache and can communicate register-to-register through a crossbar. Each processor can also switch dynamically among several threads. (TLS & SMT??) As a result, the hardware connecting processors together is quite complex and slow. However, programs executed on the M-machine can be parallelized using very fine-grain mechanisms that are impossible on an architecture that shares outside of the processor cores, like Hydra. Performance results show that on typical applications extremely fine-grained parallelization is often not as effective as parallelism at the levels that Hydra can exploit. The overhead incurred by frequent synchronizations reduces the effectiveness. Other Thread Level Speculation (TLS) Efforts: MIT M-machine