Abstract:
A processor includes a conditional branch instruction prediction mechanism that generates weighted branch prediction values. For weakly weighted predictions, which tend to be less accurate than strongly weighted predictions, the power associating with speculatively filling and subsequently flushing the cache is saved by halting instruction prefetching. Instruction fetching continues when the branch condition is evaluated in the pipeline and the actual next address is known. Alternatively, prefetching may continue out of a cache. To avoid displacing good cache data with instructions prefetched based on a mispredicted branch, prefetching may be halted in response to a weakly weighted prediction in the event of a cache miss.

Description:
BACKGROUND 
       [0001]    The present invention relates generally to the field of processors and in particular to a power efficient method of prefetching processor instructions. 
         [0002]    Portable electronic devices provide a wide variety of organizational, computational, communications and entertainment services. These devices continue to increase in both popularity and sophistication. Two relentless trends in portable electronic device evolution are increased functionality and decreased size. Increased functionality demands increased computing power—in particular, ever faster and more powerful processors. 
         [0003]    As well as providing advanced features and functionality that require faster processors, portable electronic devices themselves continue to shrink in size and weight. A major impact of this trend is the decreasing size of batteries used to power the processor and other electronics in the device. While increases in battery technology partially offset the problem, the decreasing size of batteries still imposes a strict power budget on all portable electronic device electronics, and in particular on their embedded processors. 
         [0004]    Hence, processor improvements that increase performance and/or decrease power consumption are desirable for many applications, such as most portable electronic devices. Most modern processors employ a pipelined architecture, where sequential instructions, each having multiple execution steps, are overlapped in execution. For maximum performance, the instructions should flow continuously through the pipeline. Any situation that causes instructions to be flushed from the pipeline, and subsequently restarted, detrimentally impacts both performance and power consumption. 
         [0005]    All real-world programs include conditional branch instructions, the actual branching behavior of which is not known until the instruction is evaluated deep in the pipeline. Most modern processors employ some form of branch prediction, whereby the branching behavior of conditional branch instructions is predicted early in the pipeline, and the processor speculatively fetches (prefetches) and executes instructions, based on the branch prediction. When the actual branch behavior is determined, if the branch was mispredicted, the speculatively fetched instructions must be flushed from the pipeline, and new instructions fetched from the correct next address. Prefeteching instructions in response to an erroneous branch prediction adversely impacts processor performance and power consumption. 
         [0006]    Known branch prediction techniques include both static and dynamic predictions. The likely behavior of some branch instructions can be statically predicted by a programmer and/or compiler. One example is an error checking routine. Most code executes properly, and errors are rare. Hence, the branch instruction implementing a “branch on error” function will evaluate “not taken” a very high percentage of the time. Such an instruction may include a static branch prediction bit in the opcode, set by a programmer or compiler with knowledge of the most likely outcome of the branch condition. Other branch instructions may be statically predicted based on their run-time attributes. For example, branches with a negative displacement (i.e., those that branch “backwards” in code), such as loop exit evaluations, are usually taken, while branches with a positive displacement (that branch “forward” in code) are rarely taken. Hence, the former may be statically predicted “taken,” and the latter, “not taken.” 
         [0007]    Dynamic prediction is generally based on the branch evaluation history (and in some cases the branch prediction accuracy history) of the branch instruction being predicted and/or other branch instructions in the same code. Extensive analysis of actual code indicates that recent past branch evaluation patterns may be a good indicator of the evaluation of future branch instructions. As one example of a simple branch-history branch predictor, a plurality of one-bit flags may be maintained, each indexed by address bits of a conditional branch instruction. Each flag is set when the branch evaluates “taken,” and reset when it evaluates “not taken.” The branch prediction may then simply be the value of the associated flag. For some branch instructions, this predictor may yield accurate predictions. 
         [0008]    A design goal closely related to maximizing branch prediction accuracy is minimizing the adverse impact of erroneous branch predictions. Consider the “branch on error” condition described above, with a one-bit flag as a dynamic branch predictor. Normally, the branch is not taken, and the associated flag remains a zero, predicting “not taken” for future executions of the instruction. When an error does occur, the branch is mispredicted and the wrong instructions are prefetched into the pipeline. The processor recovers from the erroneous branch prediction (sacrificing performance and wasting power), according to known branch misprediction recovery methods, and the flag is set to reflect the “taken” branch. However, the next execution of the branch instruction will still most likely be “not taken.” In this case, the single-bit branch evaluation history causes two mispredictions for each anomalous branch evaluation—one for the anomaly and another for the next subsequent execution of the branch instruction. 
         [0009]    One known technique for minimizing the deleterious effect of a mispredicted branch evaluation is to introduce the concept of a strong or weak prediction—that is, a prediction (i.e., taken or not taken) weighted by a confidence factor (e.g., strongly or weakly predicted). A simple example of this is a bimodal branch predictor comprising a table of two-bit saturating counters, indexed by memory access instruction addresses. Each counter assumes one of four states, each assigned a weighted prediction value, such as: 
         [0010]    11—Strongly predicted taken 
         [0011]    10—Weakly predicted taken 
         [0012]    01—Weakly predicted not taken 
         [0013]    00—Strongly predicted not taken 
         [0014]    The counter increments each time a corresponding branch instruction evaluates “taken” and decrements each time the instruction evaluates “not taken.” This incrementing/decrementing is “saturating,” as incrementing stops at 0b11, and decrementing stops at 0b00. Thus, the branch prediction includes not only an outcome (taken or not) but also a weighting factor indicative of the strength or confidence of the prediction. 
         [0015]    A branch instruction such as the “branch on error” considered above will only mispredict once with a saturation counter, rather than twice as with a single-bit flag predictor. The first branch prediction will move the predictor from “strongly not taken” to “weakly not taken.” The actual prediction is bimodal, and is represented by the MSB. Hence, the next occurrence of the branch instruction will still be predicted “not taken,” which is likely correct. 
         [0016]    A bimodal saturation counter may be of arbitrary size. For example, a three-bit counter may be assigned prediction confidence strengths as follows: 
         [0017]    111—Very strongly predicted taken 
         [0018]    110—Strongly predicted taken 
         [0019]    101—Predicted taken 
         [0020]    100—Moderately predicted taken 
         [0021]    011—Moderately predicted not taken 
         [0022]    010—Predicted not taken 
         [0023]    001—Strongly predicted not taken 
         [0024]    000—Very strongly predicted not taken 
         [0025]    Of course, the labels are terms of reference only; the binary value of the counter determines the strength of the branch prediction confidence, with greater confidence at either end of the range, and lower confidence towards the middle of the range. 
         [0026]    Saturation counters may track prediction accuracy as well as branch evaluation, as known in the art. The output of a saturation counter may be a weighted value of “agree” or “disagree,” and the output combined with a static prediction to arrive at a weighted prediction. In general, a broad array of branch prediction methods is known in the art, including those wherein a predictor is used not to predict the branch at all, but to select a prediction from between two or more other, independent predictors. See, for example, Scott McFarling&#39;s 1993 paper, “Combining Branch Predictors,” Digital Western Research Laboratory Technical Note TN-36, incorporated herein by reference in its entirety. 
         [0027]    While the introduction of a measure of confidence in a prediction improves branch prediction accuracy by tracking actual branch behavior over time, the actual prediction is bimodal, represented by the MSB. In the prior art, the branch is either predicted “taken” or “not taken, and prefetching proceeds from a predicted next address, which is either a branch target address or the next sequential address to the branch instruction. That is, the weighting of the prediction, or its strength, is not considered. 
       SUMMARY 
       [0028]    In one embodiment the weighting, or strength, of a branch prediction determines whether the processor prefetches instructions following a conditional branch instruction. Instructions are prefetched for strongly weighted branch predictions. Processor resources and power are conserved in the case of weakly weighted predictions by halting prefetching and waiting for the branch condition to evaluate in the pipeline. Because weakly weighted branch predictions may be less accurate than strongly weighted ones, prefetching in response to a weakly weighted prediction carries a greater likelihood of a misprediction and subsequent pipeline flush. A weakly weighted prediction may halt prefetching altogether, or alternatively may only halt prefetching in the event of a cache miss. 
         [0029]    One embodiment relates to a method of instruction prefetching in a processor having a branch prediction mechanism that generates one of a plurality of weighted branch prediction values. For strongly weighted predictions, instructions are prefetched, beginning at a predicted next address. For weakly weighted predictions, instruction prefetching is halted until the branch condition is evaluated. 
         [0030]    Another embodiment relates to a processor. The processor includes an instruction execution pipeline and a branch prediction mechanism operative to predict the evaluation of conditional branch instructions and output a weighted branch prediction value. The processor additionally includes an instruction prefetching mechanism operative to speculatively fetch instructions from a predicted next address and load them into the pipeline responsive to a strongly weighted prediction from the branch prediction mechanism, and to halt instruction prefetching responsive to a weakly weighted prediction from the branch prediction mechanism. 
         [0031]    Another embodiment relates to a method of preventing cache line replacement on mispredicted branches in a pipelined processor. The evaluation of a conditional branch instruction is predicting with a weighted value indicative of the prediction and a level of confidence in the accuracy of that prediction. a cache memory is speculatively accessed for the predicted next address following the conditional branch instruction. if the access misses in the cache and the prediction value indicates a low confidence of accuracy, a cache line replacement responsive to the miss is aborted. 
     
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         [0032]      FIG. 1  is a functional block diagram of a processor. 
           [0033]      FIG. 2  is a flow diagram of a power-efficient instruction prefetching method. 
           [0034]      FIG. 3  is a flow diagram of a power-efficient cache management method. 
       
    
    
     DETAILED DESCRIPTION 
       [0035]      FIG. 1  depicts a functional block diagram of a processor  10 . The processor  10  executes instructions in an instruction execution pipeline  12  according to control logic  14 . In some embodiments, the pipeline  12  may be a superscalar design, with multiple parallel pipelines. The pipeline  12  includes various registers or latches  16 , organized in pipe stages, and one or more Arithmetic Logic Units (ALU)  18 . A General Purpose Register (GPR) file  20  provides registers comprising the top of the memory hierarchy. 
         [0036]    The pipeline  12  fetches instructions from an instruction cache (I-cache)  22 , with memory address translation and permissions managed by an Instruction-side Translation Lookaside Buffer (ITLB)  24 . When conditional branch instructions are decoded early in the pipeline  12 , a branch prediction mechanism  23  predicts the branch behavior, and provides the prediction to an instruction prefetch unit  25 . The instruction prefetch unit  25  speculatively fetches instructions from the instruction cache  22 , from a branch target address calculated in the pipeline  12  for “taken” branch predictions, or from the next sequential address for branches predicted “not taken.” In either case, the prefetched instructions are loaded into the pipeline  12  for speculative execution. 
         [0037]    Data is accessed from a data cache (D-cache)  26 , with memory address translation and permissions managed by a main Translation Lookaside Buffer (TLB)  28 . In various embodiments, the ITLB may comprise a copy of part of the TLB. Alternatively, the ITLB and TLB may be integrated. Similarly, in various embodiments of the processor  10 , the I-cache  22  and D-cache  26  may be integrated, or unified. Misses in the I-cache  22  and/or the D-cache  26  cause an access to main (off-chip) memory  32 , under the control of a memory interface  30 . 
         [0038]    The processor  10  may include an Input/Output (I/O) interface  34 , controlling access to various peripheral devices  36 . Those of skill in the art will recognize that numerous variations of the processor  10  are possible. For example, the processor  10  may include a second-level (L2) cache for either or both the I and D caches  22 ,  26 . In addition, one or more of the functional blocks depicted in the processor  10  may be omitted from a particular embodiment. 
         [0039]    As discussed above, a wide variety of branch prediction methods and algorithms are known in the art. Regardless of the structure or methodology underlying various branch predictors, it is intuitively obvious, and may be statistically proven, that strongly weighted predictions are more accurate than weakly weighted predictions. That is, the more saturated values of the saturation counters more accurately predict branch behavior than do values toward the middle of the counters&#39; weighting ranges. The middle values represent branch instructions whose recent evaluation history is in flux; the saturated values represent branch instructions with consistent recent evaluation history. 
         [0040]    This difference in accuracy between strongly and weakly weighted branch predictions may be exploited to conserve power in a pipelined processor  10 , by only prefetching instructions for strongly predicted branch instructions. An exemplary branch prediction method is explained with reference to  FIG. 2 . A conditional branch instruction is detected in the pipeline  12  (block  40 ). This normally occurs in a decode pipe stage, but in some embodiments instructions may be predecoded prior to being loaded in the I-Cache  22 , and the pipeline control logic  14  may recognize a conditional branch instruction immediately upon instruction fetch. As soon as the instruction is detected to be a conditional branch, its evaluation (e.g., “taken” or “not taken”) is predicted (block  42 ), with a prediction having a weighed value. This weighted prediction is provided, for example, by the branch prediction mechanism  23 . The weight of the branch prediction is evaluated (block  44 ), and in the case of a strongly weighted prediction, instructions are prefetched from the I-Cache  22  and speculatively executed in the pipeline  12  (block  46 ). In the case of weakly weighted predictions, the instruction prefetch unit  25  does not prefetch any instructions (block  48 ). Rather, the prefetch unit  25  halts prefetching until the relevant conditional branch instruction is evaluated in the pipeline  12 , and its actual branch behavior is known. At that point, instruction fetching continues from the known proper next address. 
         [0041]    In effect, this methodology transforms the bimodal branch prediction of the prior art (i.e., “taken” or “not taken”) by adding a third state or directive to the prediction: predict branch taken and prefetch, predict branch not taken and prefetch, or wait for the actual branch condition evaluation. By not prefetching instructions from a weakly predicted branch target, the processor  10  does not waste the power required to prefetch instructions and begin their speculative execution, when there is a high likelihood (relative to strongly predicted branch outcomes) of the prediction being erroneous and having to flush the prefetched instructions. 
         [0042]    In the case of strongly predicted branches, the methodology of the present invention has no impact on processor performance; prefetching occurs and the branch accuracy will affect performance as well known in the art. In the case of weakly predicted branches, where prefetching is halted, the impact on processor performance depends on the accuracy of the prediction and whether the relevant potential next address—that is, the branch target address or next sequential address—is resident in the I-cache  22 . The performance impact is summarized in Table 1 below. 
         [0000]    
       
         
               
             
               
               
               
             
               
               
               
             
           
               
                 TABLE 1 
               
             
             
               
                   
               
               
                 Impact on Processor Performance 
               
             
          
           
               
                   
                 Predicted Address 
                 Predicted Address 
               
               
                   
                 hits in I-Cache 
                 misses in I-Cache 
               
               
                   
                   
               
             
          
           
               
                 Weak 
                 Stall the pipeline for 
                 Stall the pipeline for the 
               
               
                 Prediction 
                 the number of 
                 number of pipe stages 
               
               
                 Accurate 
                 pipe stages between 
                 between decode/prediction 
               
               
                   
                 decode/prediction and 
                 and branch evaluation 
               
               
                   
                 branch evaluation 
               
               
                 Weak 
                 Avoid the need to the 
                 Avoid the need to the flush 
               
               
                 Prediction 
                 flush pipeline and 
                 pipeline and recover from 
               
               
                 Erroneous 
                 recover from 
                 the misprediction, and avoid 
               
               
                   
                 the misprediction 
                 displacing good data in I- 
               
               
                   
                   
                 Cache with unneeded instructions 
               
               
                   
               
             
          
         
       
     
         [0043]    If the weakly weighted branch prediction is accurate, halting instruction prefetching reduces performance by introducing a stall in the pipeline. Instruction execution will be stalled (relative to having done the prefetching) by the number of pipe stages between the branch instruction decode and branch prediction, and the eventual branch condition evaluation. In this case, there will be no power savings, as the same instructions will ultimately be fetched and executed. 
         [0044]    If the weakly weighted branch prediction is erroneous, however, not only does the prefetch halting methodology of the present invention save power, it may improve processor performance. If the predicted address is resident in the I-Cache  22 , the processor  10  incurs the same stall as in the case of an accurate weakly weighted branch prediction. However, the controller  14  does not need to flush the pipeline  12  and engage in other misprediction recovery operations. Where a mispredicted branch requires an exception for recovery, having halted instruction prefetching represents a significant increase in processor performance over prefetching. 
         [0045]    If the weakly weighted branch prediction is erroneous and the predicted address is not resident in the I-Cache  22 , the prefetch halting methodology of the present invention saves power and considerably improves processor performance. In this case, the prefetch operation would miss in the I-Cache  22 , causing a memory access and a cache line replacement. Accesses to external memory are slow and consume power, adversely impacting both performance and power management. Worse, however, the operation would displace an entire cache line with instructions that the processor  10  does not need to execute. This will likely cause a subsequent cache miss when the displaced instructions are again fetched, requiring the delay and power expenditure of yet another external memory access. 
         [0046]    In one embodiment of the present invention, instruction prefetching is not completely halted in response to weakly weighted branch predictions; rather it is halted only if a prefetch misses in the I-Cache  22 , as described with reference to  FIG. 3 . As described above, a conditional branch instruction is detected (block  40 ) and its evaluation predicted (block  42 ). If the prediction is strongly weighted, instructions are prefetched from a predicted next address (block  46 ). If the prediction is weakly weighted, the instruction prefetch unit  25  accesses the I-Cache  22  to determine whether the predicted next address is resident therein (block  50 ). If the predicted address hits in the I-Cache  22 , prefetching continues (block  52 ). If the prefetch operation misses in the I-Cache  22 , then the prefetch operation is terminated, and prefetching is halted until the branch condition is evaluated in the pipeline  12  (block  54 ). In this embodiment, the stall in the event of an accurate weakly weighted branch prediction is avoided, while still safeguarding against the significant performance degradation incurred by a cache line replacement for an erroneous weakly weighted branch prediction. 
         [0047]    Regardless of whether weakly weighted branch predictions completely halt instruction prefetching or only halt prefetching in the case of an I-Cache miss, in any given implementation, what constitutes a “weak” or “strong” prediction weighting must be defined. In applications where power savings are tantamount and some performance degradation is tolerable, a strongly weighted prediction may comprise only the most saturated values of a saturation counter. That is, from a hardware perspective, if all of the counter bits agree, the prediction is strongly weighted and prefetching is enabled; if any counter bits disagree, the prediction may be considered weakly weighted, and prefetching totally or conditionally disabled. 
         [0048]    Where power savings is less critical and/or performance is more important, a more flexible approach may include counter values near, as well as at, the saturation level in the definition of strongly weighted. As one non-limiting example, the top and bottom 25% of counter values may be considered strongly weighted, and the middle 50% weakly weighted. For binary counters, a hardware perspective of this distribution is that if the two most significant bits agree, the prediction value is strongly weighted. Alternatively, the upper and lower third may be considered strongly weighted, and the middle thirds weakly weighted. Those of skill in the art will readily recognize the distinction between strongly and weakly weighted predictions may be defined in a variety of ways, as may be appropriate for a particular application. 
         [0049]    As used herein, the terms strong and weak, and derivations thereof, are terms of reference. In particular, they refer to the outputs of any branch predictor that generates a weighted output indicative of a branch prediction and a level of confidence in the accuracy of that prediction, wherein strongly weighted refers to outputs indicating a high confidence and weakly weighted refers to outputs indicating a low confidence. Any processor  10  that completely or conditionally halts instruction prefetching and/or speculative instruction execution in response to a weakly weighted branch prediction is within the scope of the present invention. 
         [0050]    Although the present invention has been described herein with respect to particular features, aspects and embodiments thereof, it will be apparent that numerous variations, modifications, and other embodiments are possible within the broad scope of the present invention, and accordingly, all variations, modifications and embodiments are to be regarded as being within the scope of the invention. The present embodiments are therefore to be construed in all aspects as illustrative and not restrictive and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.