The Soft Error Problem: an Architectural Perspective Shubhendu S

The Soft Error Problem: an Architectural Perspective Shubhendu S

The Soft Error Problem: An Architectural Perspective Shubhendu S. Mukherjee,1 Joel Emer,2 and Steven K. Reinhardt1,3 1 FACT Group 2 VSSAD 3 Advanced Computer Architecture Lab Intel Corporation Intel Corporation EECS Department, University of Michigan 77 Reed Road, Hudson MA 01749 77 Reed Road, Hudson MA 01749 1301 Beal Avenue, Ann Arbor, MI 48109 [email protected] [email protected] [email protected] 1. Introduction 2.1. SDC & DUE Radiation-induced soft errors have emerged as a key challenge Figure 1 illustrates the possible outcomes of a single-bit fault. in computer system design. Exponentially increasing transistor Outcomes labeled 1-3 indicate non-error conditions. The most counts will drive per-chip fault rates correspondingly higher unless insidious form of error is silent data corruption (SDC) (outcome new technologies are employed. If our industry is to continue to 4), where a fault induces the system to generate erroneous outputs. provide customers with the level of reliability they expect, micro- To avoid SDC, designers often employ basic error detection mech- processor architects must address this challenge directly. This anisms, such as parity. effort has two parts. First, architects must understand the impact of With the ability to detect a fault but not correct it, we avoid soft errors on their designs. Second, they must select judiciously generating incorrect outputs, but cannot recover when an error from among available techniques to reduce this impact in order to occurs. In other words, simple error detection does not reduce the meet their reliability targets with minimum overhead. overall error rate, but does provide fail-stop behavior and thereby The research community can play a significant role in both of avoids any data corruption. We call errors in this category detected these areas. On the first front, we must develop better conceptual unrecoverable errors (DUE). Currently, the industry specifies soft frameworks, analysis techniques, and software tools to advance error rates in terms of SDC and DUE numbers. both intuitive understanding and quantitative measurement of how We further subdivide DUE events according to whether the soft errors affect system behavior. On the second front, we must detected fault would have affected the final outcome of the execu- expand and characterize the space of soft error avoidance, detec- tion. We call benign detected faults false DUE events (outcome 5 tion, and recovery techniques so that solutions are available to of Figure 1) and others true DUE events (outcome 6). A conserva- reach various reliability targets within realistic performance, tive system that signals all detected faults as processor failures will power, area, and complexity constraints. unnecessarily raise the DUE rate by failing on false DUE events. Alternatively, if the processor can identify false DUE events (e.g., To provide a foundation for these efforts, this paper gives a the fault corrupted only the result of a wrong-path instruction), broad overview of the soft error problem from an architectural per- then it can suppress the error signal. spective. We start with basic definitions (Section 2) followed by a description of techniques to compute the soft error rate (Section 3). DUE events can also be divided into process-kill and system- Then, we summarize techniques used to reduce the soft error rate kill categories (not shown in Figure 1). In some cases, such as a (Section 4). Section 5 describes problems we face with double-bit parity error on an architectural register, an operating system (OS) errors. Finally, in Section 6 we outline future directions for archi- can isolate the error to a specific process or set of processes. The tecture research in soft errors. Table 1 provides a summary of acro- OS can then kill the affected process or processes but leave the rest nyms used in this paper. of the system running. We call such a DUE event process-kill 2. Background and Metrics faulty bit is Transient faults arise from energetic particles—such as neu- read? no yes trons from cosmic rays and alpha particles from packaging mate- rial—generating electron-hole pairs as they pass through a semiconductor device. Transistor source and diffusion nodes can benign fault; 1 bit has collect these charges. A sufficient amount of accumulated charge no error error protection? may invert the state of a logic device—such as an SRAM cell, a latch, or a gate—thereby introducing a logical fault into the cir- detection & detection cuit’s operation. Because this type of fault does not reflect a per- fault corrected; correction no 2 only manent failure, it is termed soft or transient. no error Current trends suggest that soft errors from particle strikes will be an increasing burden for microprocessor designers in future. affects program affects program The raw error rate per device (e.g., latch, SRAM cell) in a bulk outcome? outcome? CMOS process is projected to remain roughly constant or decrease no yes no slightly for the next several technology generations [6][7]. Thus, yes unless we add more extensive error protection mechanisms or use a more robust technology (such as SOI), a processor’s error rate benign fault; will grow in direct proportion to the number of devices we add to a 3 no error 4 SDC5 false DUE6 true DUE processor in each succeeding generation. In contrast, however, by slowing the reduction of cell capacitance and supply voltage, Figure 1. Classification of the possible outcomes of a DRAM vendors have managed to reduce the soft error rate per bit faulty bit in a microprocessor. SDC = silent data corrup- with every technology generation [2]. tion. DUE = detected unrecoverable error. Table 1: Glossary of Acronyms next section discusses the device error rate, while the following Term Explanation section describes the SDC and DUE AVFs. FIT Failure in Time, 1 FIT = 1 failure in a billion hours 3.1. Device Error Rate MTTF Mean Time to Failure The device error rate (measured in FIT) is the product of the SER Soft Error Rate particle flux and the underlying circuit error rate determined by the SDC Silent Data Corruption technology and implementation. To the first order, the error rate is DUE Detected Unrecoverable Error directly proportional to the particle flux rate. Alpha particles typi- ACE Architecturally Correct Execution cally arise from contamination in the packaging material, solder, un-ACE Unnecessary for Architecturally Correct Execution etc. Special shielding materials can dramatically reduce the impact of alpha particles on semiconductor devices. Terrestrial neutrons AVF Architectural Vulnerability Factor arise when cosmic rays coming from deep space interact with the TVF Timing Vulnerability Factor earth’s atmosphere. Several feet of concrete are required for neu- PVF Propagation Vulnerability Factor tron shielding, which is impractical for most applications. Neutron DUE. The remaining DUE events fall into the system-kill DUE flux increases with altitude. For example, at 1.5km in Denver, Col- category, as the only recourse is to bring down the entire system. orado (USA) the flux is approximately 5x higher than at sea level, 2.2. FIT & MTTF while in an airplane flying at 10,000 km it is about 100x higher. Both SDC and DUE rates are typically expressed in FIT (Fail- The circuit error rate for RAM cells, latches, and dynamic cir- ure(s) in Time). One FIT signifies one error in a billion (109) hours. cuits is the product of the raw circuit error rate and a timing vulner- FIT rates are additive, so we can compute the SDC or DUE FIT ability factor (TVF). The raw circuit error rate indicates the rate of a chip or system by summing the SDC or DUE FIT rates of likelihood of a specific cell experiencing a bit flip. The minimum all its components. The sum of SDC and DUE FIT is usually charge required to flip a cell is called Qcrit. Qcrit depends on the referred to as the soft error rate (SER) of a chip. cell’s capacitance and voltage. The amount of charge a circuit can The additive property of FIT makes it convenient for calcula- collect, depends on its area and its collection efficiency, which is a tions, but Mean Time to Failure (MTTF) is often more intuitive. measure of the amount of charge generated from a particle strike. MTTF is inversely related to FIT. A FIT rate of 1000 is equivalent For dynamic circuits, we must factor in the error masking effects to MTTF of 114 years (= 109 / (1000 X 24 X 365)). from a strike on any of the pull-down nodes. Both MTTF and FIT are defined relative to the domain over The raw error rate of a cell can be computed by simulating which the corresponding FIT contribution is computed. For exam- current pulses of all magnitude on all nodes of a cell at different ple, the FIT rate of a complete computer system can be quite low points of time. Unfortunately, this can be very compute intensive. even though individual system components have a higher FIT rate, Hence, for full-chip simulations, usually we use approximate mod- e.g., as in a triple-modular redundant system (see Section 4.3.2). els or Monte Carlo simulation techniques. Vendors typically set soft-error-rate budgets for their chips or We derate the circuit’s raw error rate by its TVF. The TVF is systems based on target market requirements. For example, IBM the fraction of each cycle during which a bit flip in a cell will be targets 114 SDC FIT (1000 yr MTTF), 4,566 system-kill DUE FIT captured. RAM cells are typically always vulnerable; thus their (25 yr MTTF), and 11,415 process-kill DUE FIT (10 yr MTTF) for TVF is 100%.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    5 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us