US 7,607,038 B2Grant
Systems and methods for CPU repair
Issue Date:2009-10-20
•34 Claims
•7 Drawing Sheets
Abstract
In one embodiment, a method for repairing a faulty cache element is provided. Once a monitored cache element is determined to be faulty, the system stores the repair information, and cache configuration in an EEPROM or non-volatile memory on the CPU module. Then the computer is rebooted. During the reboot, the faulty cache element is repaired by being swapped out for a spare cache element based on the information stored in the EEPROM or the non-volatile memory.
Metadata
Assignee
- Hewlett-Packard Development Company, L.P.
Inventors
- Jeff Barlow
- Jeff Brauch
- Howard Calkin
- Raymond Gratias
- Stephen Hack
- Lacey Joyal
- Guy Kuntz
- Ken Pomaranski
- Michael Sedmak
Application Information
Application Number:US 11/357,384
Filing Date:2006-02-17
Priority Date:2005-02-18
Art Unit:2113
Classifications
IPC:
G06F11/00
Patent Drawings (7 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims priority from U.S. Provisional application Ser. No. 60/654,272 filed on Feb. 18, 2005.
[0002] This application is also related to the following U.S. patent applications:
[0003] “Systems and Methods for CPU Repair”, Ser. No. 60/654,741, filed Feb. 18, 2005; Ser. No. 11/356,756, filed Feb. 17, 2006 having the same title;
[0004] “Systems and Methods for CPU Repair”, Ser. No. 60/654,259, filed Feb. 18, 2005; Ser. No. 11/356,559, filed Feb. 17, 2006 having the same title;
[0005] “Systems and Methods for CPU Repair”, Ser. No. 60/654,255, filed Feb. 18, 2005; Ser. No. 11/356,564, filed Feb. 17, 2006 having the same title;
[0006] “Systems and Methods for CPU Repair”, Ser. No. 60/654,256, filed Feb. 18, 2005; Ser. No. 11/356,576, filed Feb. 17, 2006 having the same title;
[0007] “Systems and Methods for CPU Repair”, Ser. No. 60/654,740, filed Feb. 18, 2005; Ser. No. 11/536,521, filed Feb. 17, 2006 having the same title;
[0008] “Systems and Methods for CPU Repair”, Ser. No. 60/654,739, filed Feb. 18, 2005; Ser. No. 11/537,396, filed Feb. 17, 2006 having the same title;
[0009] “Systems and Methods for CPU Repair”, Ser. No. 60/654,258, filed Feb. 18, 2005; Ser. No. 11/356,560, filed Feb. 17, 2006 having the same title;
[0010] “Systems and Methods for CPU Repair”, Ser. No. 60/654,744, filed Feb. 18, 2005; Ser. No. 11/536,548, filed Feb. 17, 2006 having the same title;
[0011] “Systems and Methods for CPU Repair”, Ser. No. 60/654,743, filed Feb. 18, 2005; Ser. No. 11/357,386, filed Feb. 17, 2006 having the same title;
[0012] “Methods and Systems for Conducting Processor Health-Checks”, Ser. No. 60/654,603, filed Feb. 18, 2005; Ser. No. 11/357,385, filed Feb. 17, 2006 having the same title; and
[0013] “Methods and Systems for Conducting Processor Health-Checks”, Ser. No. 60/654,273, filed Feb. 18, 2005; Ser. No. 11/356,759, filed Feb. 17, 2006 having the same title;
[0014] which are fully incorporated herein by reference.
Background
[0015] At the heart of many computer systems is the microprocessor or central processing unit (CPU) (referred to collectively as the “processor.”) The processor performs most of the actions responsible for application programs to function. The execution capabilities of the system are closely tied to the CPU: the faster the CPU can execute program instructions, the faster the system as a whole will execute.
[0016] Early processors executed instructions from relatively slow system memory, taking several clock cycles to execute a single instruction. They would read an instruction from memory, decode the instruction, perform the required activity, and write the result back to memory, all of which would take one or more clock cycles to accomplish.
[0017] As applications demanded more power from processors, internal and external cache memories were added to processors. A cache memory (hereinafter cache) is a section of very fast memory located within the processor or located external to the processor and closely coupled to the processor. Blocks of instructions or data are copied from the relatively slower system memory (DRAM) to the faster cache memory where they can be quickly accessed by the processor.
[0018] Cache memories can develop persistent errors over time, which degrade the operability and functionality of their associated CPU's. In such cases, physical removal and replacement of the failed or failing cache memory has been performed. Moreover, where the failing or failed cache memory is internal to the CPU, physical removal and replacement of the entire CPU module or chip has been performed. This removal process is generally performed by field personnel and results in greater system downtime.
Summary
[0019] In one embodiment, a method for repairing a faulty cache element is provided. Once a monitored cache element is determined to be faulty, the system stores the repair information, and cache configuration in a non-volatile memory or an EEPROM on the CPU module. The computer is rebooted. During the reboot, the faulty cache element is repaired by being swapped out for a spare cache element based on the information stored in the non-volatile memory or EEPROM.
Brief Description of the Drawings
[0020] FIG. 1 is an exemplary overall system diagram;
[0021] FIG. 2 is an exemplary diagram of a CPU cache management system;
[0022] FIG. 3 is a high level flow chart of cache management logic;
[0023] FIG. 4 is a flow chart of the cache management logic; and
[0024] FIG. 5 is a flow chart of the repair process of the cache management logic.
Detailed Description of the Invention
[0025] The following includes definition of exemplary terms used throughout the disclosure. Both singular and plural forms of all terms fall within each meaning:
[0026] “Logic”, as used herein includes, but is not limited to, hardware, firmware, software and/or combinations of each to perform a function(s) or an action(s). For example, based on a desired application or needs, logic may include a software controlled microprocessor, discrete logic such as an application specific integrated circuit (ASIC), or other programmed logic device. Logic may also be fully embodied as software.
[0027] “Cache”, as used herein includes, but is not limited to, a buffer or a memory or section of a buffer or memory located within a processor (“CPU”) or located external to the processor and closely coupled to the processor.
[0028] “Cache element”, as used herein includes, but is not limited to, one or more sections or sub-units of a cache.
[0029] “CPU”, as used herein includes, but is not limited to, any device, structure or circuit that processes digital information including for example, data and instructions and other information. This term is also synonymous with processor and/or controller.
[0030] “Cache management logic”, as used herein includes, but is not limited to, any logic that can store, retrieve, and/or process data for exercising executive, administrative, and/or supervisory direction or control of caches or cache elements.
[0031] “During”, as used herein includes, but is not limited to, in or throughout the time or existence of; at some point in the entire time of; and/or in the course of.
[0032] “Non-volatile memory”, as used herein includes, but is not limited to any memory in which retention of data does not rely on power to preserve it.
[0033] Referring now to FIG. 1 , a computer system 100 constructed in accordance with one embodiment generally includes a central processing unit (“CPU”) 102 coupled to a host bridge logic device 106 over a CPU bus 104. CPU 102 may include any processor suitable for a computer such as, for example, a Pentium or Centrino class processor provided by Intel. A system memory 108, which may be is one or more synchronous dynamic random access memory (“SDRAM”) devices (or other suitable type of memory device), couples to host bridge 106 via a memory bus. Further, a graphics controller 112, which provides video and graphics signals to a display 114, couples to host bridge 106 by way of a suitable graphics bus, such as the Advanced Graphics Port (“AGP”) bus 116. Host bridge 106 also couples to a secondary bridge 118 via bus 117.
[0034] A display 114 may be a Cathode Ray Tube, liquid crystal display or any other similar visual output device. An input device is also provided and serves as a user interface to the system. As will be described in more detail, input device may be a light sensitive panel for receiving commands from a user such as, for example, navigation of a cursor control input system. Input device interfaces with the computer system's I/O such as, for example, USB port 138. Alternatively, input device can interface with other I/O ports.
[0035] Secondary Bridge 118 is an I/O controller chipset. The secondary bridge 118 interfaces a variety of I/O or peripheral devices to CPU 102 and memory 108 via the host bridge 106. The host bridge 106 permits the CPU 102 to read data from or write data to system memory 108. Further, through host bridge 106, the CPU 102 can communicate with I/O devices on connected to the secondary bridge 118 and, and similarly, I/O devices can read data from and write data to system memory 108 via the secondary bridge 118 and host bridge 106. The host bridge 106 may have memory controller and arbiter logic (not specifically shown) to provide controlled and efficient access to system memory 108 by the various devices in computer system 100 such as CPU 102 and the various I/O devices. A suitable host bridge is, for example, a Memory Controller Hub such as the Intel® 875P Chipset described in the Intel® 82875P (MCH) Datasheet, which is hereby fully incorporated by reference.
[0036] Referring still to FIG. 1 , secondary bridge logic device 118 may be an Intel® 82801EB I/O Controller Hub 5 (ICH5)/Intel® 82801ER I/O Controller Hub 5R (ICH5R) device provided by Intel and described in the Intel® 82801EB ICH5/82801ER ICH5R Datasheet, which is incorporated herein by reference in its entirety. The secondary bridge includes various controller logic for interfacing devices connected to Universal Serial Bus (USB) ports 138, Integrated Drive Electronics (IDE) primary and secondary channels (also known as parallel ATA channels or sub-system) 140 and 142, Serial ATA ports or sub-systems 144, Local Area Network (LAN) connections, and general purpose I/O (GPIO) ports 148. Secondary bridge 118 also includes a bus 124 for interfacing with BIOS ROM 120, super I/O 128, and CMOS memory 130. Secondary bridge 118 further has a Peripheral Component Interconnect (PCI) bus 132 for interfacing with various devices connected to PCI slots or ports 134-136. The primary IDE channel 140 can be used, for example, to couple to a master hard drive device and a slave floppy disk device (e.g., mass storage devices) to the computer system 100. Alternatively or in combination, SATA ports 144 can be used to couple such mass storage devices or additional mass storage devices to the computer system 100.
[0037] The BIOS ROM 120 includes firmware that is executed by the CPU 102 and which provides low level functions, such as access to the mass storage devices connected to secondary bridge 118. The BIOS firmware also contains the instructions executed by CPU 102 to conduct System Management Interrupt (SMI) handling and Power-On-Self-Test (“POST”) 122. POST 102 is a subset of instructions contained with the BIOS ROM 102. During the boot up process, CPU 102 copies the BIOS to system memory 108 to permit faster access.
[0038] The super I/O device 128 provides various inputs and output functions. For example, the super I/O device 128 may include a serial port and a parallel port (both not shown) for connecting peripheral devices that communicate over a serial line or a parallel pathway. Super I/O device 108 may also include a memory portion 130 in which various parameters can be stored and retrieved. These parameters may be system and user specified configuration information for the computer system such as, for example, a user-defined computer set-up or the identity of bay devices. The memory portion 130 in National Semiconductor's 97338VJG is a complementary metal oxide semiconductor (“CMOS”) memory portion. Memory portion 130, however, can be located elsewhere in the system.
[0039] Referring to FIG. 2 , one embodiment of the CPU cache management system 200 is shown. CPU cache management system 200 includes a CPU chip 201 having various types of cache areas 202, 203, 204, 205. Although only one CPU chip is shown in FIG. 2 , more than one CPU chip may be used in the computer system 100. The types of cache area may include, but is not limited to, D-cache elements, I-cache elements, D-cache element tags, and I-cache element tags. The specific types of cache elements are not critical.
[0040] Within each cache area 202, 203, 204, 205 are at least two subsets of elements. For example, FIG. 2 shows the two subsets of cache elements for cache area 203. The first subset includes data cache elements 206 that are initially being used to store data. The second subset includes spare cache elements 207 that are identical to the data cache elements 206, but which are not initially in use. When the CPU cache areas are constructed, a wafer test is applied to determine which cache elements are faulty. This is done by applying multiple voltage extremes to each cache element to determine which cache elements are operating correctly. If too many cache elements are deemed faulty, the CPU is not installed in the computer system 100. At the end of the wafer test, but before the CPU is installed in the computer system 100, the final cache configuration is laser fused in the CPU chip 201. Thus, when the computer system 100 is first used, the CPU chip 201 has permanent knowledge of which cache elements are faulty and is configured in such a way that the faulty cache elements are not used.
[0041] As such, the CPU chip 201 begins with a number of data cache elements 206 that have passed the wafer test and are currently used by the CPU chip. In other words, the data cache elements 206 that passed the wafer test are initially presumed to be operating properly and are thus initially used or allocated by the CPU. Similarly, the CPU chip begins with a number of spare or non-allocated cache elements 207 that have passed the wafer test and are initially not used, but are available to be swapped in for data cache elements 206 that become faulty.
[0042] Also included in the CPU cache management system 200 is logic 212. In the exemplary embodiment of FIG. 2 , the logic 212 is contained in the CPU core logic. However, logic 212 may be located, stored or run in other locations. Furthermore, the logic 212 and its functionality may be divided up into different programs, firmware or software and stored in different locations.
[0043] Connected to the CPU chip 201 is an interface 208. The interface 208 allows the CPU chip 201 to communication with and share information with a non-volatile memory 209 and a boot ROM. The boot ROM contains data and information needed to start the computer system 100 and the non-volatile memory 209 may contain any type of information or data that is needed to run programs or applications on the computer system 100, such as, for example, the cache element configuration.
[0044] Now referring to FIG. 3 , a high level flow chart of an exemplary process of the cache management logic 300 is shown. The rectangular elements denote “processing blocks” and represent computer software instructions or groups of instructions. The diamond shaped elements denote “decision blocks” and represent computer software instructions or groups of instructions which affect the execution of the computer software instructions represented by the processing blocks. Alternatively, the processing and decision blocks represent steps performed by functionally equivalent circuits such as a digital signal processor circuit or an application-specific integrated circuit (ASIC). The flow diagram does not depict syntax of any particular programming language. Rather, the flow diagram illustrates the functional information one skilled in the art may use to fabricate circuits or to generate computer software to perform the processing of the system. It should be noted that many routine program elements, such as initialization of loops and variables and the use of temporary variables are not shown.
[0045] The cache management logic refers generally to the monitoring, managing, handling, storing, evaluating and/or repairing of cache elements and/or their corresponding cache element errors. Cache management logic can be divided up into different programs, routines, applications, software, firmware, circuitry and algorithms such that different parts of the cache management logic can be stored and run from various different locations within the computer system 100. In other words, the implementation of the cache management logic can vary.
[0046] The cache management logic 300 begins after the operating system of the computer system 100 is up and running. During boot up of the computer system 100, the CPU 201 may have a built-in self test, independent of the cache management logic, in which the cache elements are tested to make sure that they are operating correctly. However, the testing must be performed during the booting process. This results in greater downtime and less flexibility since the computer system 100 must be rebooted in order to determine if cache elements are working properly. However, as shown in FIG. 3 , the cache management logic may be run while the operating system is up and running. As a result, the computer system 100 may monitor and locate faulty cache elements continuously without having to reboot the computer system. Thus, the computer system 100 knows of faulty cache elements sooner and can repair the faulty cache elements sooner.
[0047] While the operating system is running, the cache management logic 300 determines whether any of the currently-used cache elements within the CPU are faulty (step 301). This is accomplished, for example, by totaling the number of errors that each cache element accumulates using or implementing a standard error-correction code (ECC) within the CPU and comparing that totaled number against a predetermined threshold. If a currently-used cache element is not faulty (step 301), the cache management logic simply returns to normal operation (step 305). However, if a currently-used cache element is determined to be faulty (step 301), the cache management logic, at step 302, stores the repair information in the CPU EEPROM, and stores the CPU serial number and cache configuration in the non-volatile memory 209. It is possible to also store the repair information, CPU serial number and cache configuration entirely in the EEPROM without storing such information in the non-volatile memory. The computer system 100 is subsequently rebooted at step 303. Then, the cache management logic 300 swaps in a spare cache element for the faulty cache element during the next system reboot, at step 304. The cache management logic then returns to its normal monitoring operation at step 305.
[0048] Now referring to FIG. 4 , an exemplary process of the cache management logic 300 is shown in the form of a flowchart 400. The cache management logic refers generally to the monitoring, managing, handling, storing, evaluating and repairing of cache elements and their corresponding cache element errors. Cache management logic can be divided up into different programs, routines, applications, software, firmware, circuitry and algorithms such that different parts of the cache management logic can be stored and run from various different locations within the computer system 100. In other words, the implementation of the cache management logic may vary.
[0049] In the embodiment shown in FIG. 4 , the cache management logic begins by having logic within the operating system 401 monitor the CPU cache for cache element errors in step 402. While the embodiment shown in FIG. 4 illustrates that the monitoring is performed by part of the cache management logic in the operating system, the monitoring may also be performed from a diagnostics program running on the system firmware as well. During the monitoring of the cache elements, the cache management logic determines that a cache element is faulty, based on, for example, the number of errors occurring in a particular cache element exceeding a predetermined threshold number. If the monitoring process determines that a cache element needs to be repaired, the repair information is stored in the non-volatile memory and/or EEPROM (step 403) and the system administration is informed that a reboot is required (step 404). The repair information includes, for example, the physical address of the faulty cache element.
[0050] Subsequently, the machine or computer system 100 is shutdown and rebooted (step 405). During the reboot, the system firmware (part of the cache management logic, 406) reads cache fuse data from the CPU and stores that fuse information into the non-volatile memory and/or EEPROM (step 407). Subsequently, the system firmware reads the cache configuration from the non-volatile memory and/or EEPROM (step 408). Then, with the cache configuration read, the system firmware initializes each cache (step 409). The cache initialization process is explained in more detail below with respect to FIG. 5 . After the caches are initialized and all necessary cache element repairs are successfully made, the system firmware finishes booting the machine and performing normal system self-test on the way to booting the operating system (step 410).
[0051] Referring now to FIG. 5 , one embodiment of the cache initialization process 500 is illustrated. The process begins by looping through each cache element or through the cache error log data, in step 501, and repairing cache elements as needed based on, for example, the earlier determined cache repair information. For each cache element, the cache management logic determines, based on the cache repair information that was read from the non-volatile memory and/or EEPROM, if the cache element needs to be repaired (step 502). If the cache element does not need to be repaired, the process loops through the next cache element (step 507).
[0052] However, if the cache element is in need of repair, the cache management logic determines if a spare cache element is available (step 503). In making this determination, the cache management logic may utilize any spare cache element 207 that is available. In other words, there is no predetermined or pre-allocated spare cache element 207 for a particular cache element 206. Any available spare cache element 207 may be swapped in for any cache element 206 that become faulty. If a spare cache element is not available, the cache management logic de-allocates the CPU (step 508). If a spare cache element is available, the cache management logic swaps in the spare cache element for the faulty cache element (step 504). The “swapping in” process refers generally to the replacement of one component by another including, for example, the reconfiguration and re-allocation within the computer system 100 and its memory 108 such that the computer system 100 recognizes and utilizes the spare (or swapped in) component in place of the faulty (or de-allocated) component, and no longer utilizes the faulty (or de-allocated) component. The “swapping in” process for cache elements may be accomplished, for example, by using associative addressing. More specifically, each spare cache element may have an associative addressing register and a valid bit associated with it. To repair a faulty cache element, the address of the faulty cache element is entered into the associative address register on one of the spare cache elements, and the valid bit is turned on. The hardware may then automatically access the replaced element rather than the original cache element.
[0053] Once the spare cache element is swapped in for the faulty cache element, the cache configuration is updated in the non-volatile memory and/or EEPROM (step 505). A spare cache element may be swapped in for a previously swapped in spare cache element that has become faulty. Hereinafter, such swapping refers to any process by which the spare cache element is mapped for having data stored therein or read therefrom in place of the faulty cache element. In one embodiment, this can be accomplished by de-allocating the faulty cache element and allocating the spare cache element in its place. Subsequently, the cache management logic reports that the cache element has been successfully repaired (step 506) and the process loops through the next cache element (step 507). The looping continues until each cache element has been addressed, at which time the cache initialization is considered finished (step 509) and the system firmware finishes booting the machine (step 410).
[0054] Due to the number of repairs that may occur to a computer system 100 having multiple CPUs, it is desirable to ensure that the cache configuration is remembered throughout each system reboot. As stated above, each time a cache element is repaired, the updated cache configuration is stored in the non-volatile memory or EEPROM. The non-volatile memory keeps track of each CPU in the computer system 100. Also, the non-volatile memory is indexed by the serial number of each of the CPUs in the computer system 100. The EEPROM provides a permanent storage for cache related information that may physically stay with the corresponding CPU.
[0055] Upon system boot up, prior to reading the cache fuse data or the cache repair information, the serial number of each CPU is compared to the serial number stored with the cache repair information in the non-volatile memory and/or EEPROM. If the serial number of the CPU matches the serial number stored with the cache repair information in the non-volatile memory and/or EEPROM, then the system firmware reads the data stored in the non-volatile memory and/or EEPROM. The system firmware also reads the cache configuration from the non-volatile memory and/or EEPROM (step 408).
[0056] However, if the CPU serial number does not match the serial number stored in the non-volatile memory, then the system firmware clears out the cache information in the non-volatile memory related to any unmatched CPU serial number. Then, the system firmware reads the burned cache fuse date from the CPU and stores that information into the non-volatile memory and/or EEPROM. This step is necessary to ensure that the CPU cache configuration is utilized for the correct CPU. Since CPUs may get pulled and replaced by new CPUs, upon boot up, the system confirms that the cache configuration information in the non-volatile memory and/or EEPROM is for the appropriate CPU. Finally, the system reads the repair information from the non-volatile memory and/or EEPROM. The repair information is then used to make the needed repairs during system boot up.
[0057] Additionally, if the repair information is stored on the EEPROM, it provides the advantage of traveling with the CPU module. For example, if the CPU module is removed from the computer, the EEPROM, which may be a part of the CPU module, travels with the CPU module. As a result, the repair information travels with the CPU and can be called up during analysis or by another different computer.
[0058] While the present invention has been illustrated by the description of embodiments thereof, and while the embodiments have been described in considerable detail, it is not the intention of the applicants to restrict or in any way limit the scope of the appended claims to such detail. Additional advantages and modifications will readily appear to those skilled in the art. For example, the number of spare cache elements, spare CPUs, and the definition of a faulty cache or memory can be changed. Therefore, the inventive concept, in its broader aspects, is not limited to the specific details, the representative apparatus, and illustrative examples shown and described. Accordingly, departures may be made from such details without departing from the spirit or scope of the applicant's general inventive concept.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method for repairing a faulty cache element associated with a CPU in a computer system, said method comprising the steps of:
determining that a cache element is faulty;
storing repair information, a CPU serial number, and cache configuration in a non-volatile memory;
rebooting said computer system;
swapping in a spare cache element for said faulty cache element during system reboot;
reading a CPU serial number from said CPU;
comparing the read CPU serial number with the stored CPU serial number; and
clearing said repair information and said cache configuration from said non-volatile memory if the stored CPU serial number does not match the read CPU serial number.
2. The method of claim 1, further comprising the steps of:
reading burned cache fuse data from said CPU; and
storing said burned cache data into said non-volatile memory.
3. The method of claim 1, further comprising the steps of:
reading burned cache fuse data from said CPU if the stored CPU serial number matches the read CPU serial number;
storing said read burned cache fuse data into said non-volatile memory; and
reading said cache configuration from said non-volatile memory.
4. The method of claim 1 wherein said non-volatile memory is an EEPROM.
5. A method for repairing a processor, said method comprising the steps of:
determining that an allocated cache element associated with said processor is faulty and in need of repair;
storing repair information into a non-volatile memory;
storing a processor serial number;
swapping in a spare cache element for said faulty allocated cache element during system reboot;
reading a processor serial number from said processor;
comparing the read processor serial number with the stored processor serial number; and
clearing said repair information and said cache configuration from said non-volatile memory if the stored processor serial number does not match the read processor serial number.
6. The method of claim 5, further comprising the steps of: monitoring for a cache error while an operating system is running; and recording cache error information in said non-volatile memory; and generating said system reboot.
7. The method of claim 5, further comprising the step of: determining whether said spare cache element is available if said currently-used cache element is determined to be faulty during said system reboot.
8. The method of claim 5, further comprising the step of: reporting actions taken and updating cache configuration in said non-volatile memory.
9. The method of claim 5, wherein said non-volatile memory is an EEPROM.
10. A CPU cache element management system comprising:
a CPU having a currently-used cache element and a spare cache element;
a cache management logic operable to: determine whether currently-used cache elements are faulty and store a CPU serial number; swap in said spare cache element for said currently-used cache element during a system reboot; read a CPU serial number from said CPU; and compare the read CPU serial number with the stored CPU serial number; and
a non-volatile memory operable to store cache configuration, repair information and CPU serial numbers, wherein said repair information and said cache configuration are removable from said non-volatile memory if the stored CPU serial number does not match the read CPU serial number.
11. The CPU cache element management system of claim 10, wherein said cache management logic is further operable to monitor cache errors and record cache error information in said non-volatile memory.
12. The CPU cache management system of claim 10, wherein said cache management logic is further operable to determine, during system reboot, whether said spare cache element is available if said currently-used cache element is determined to be faulty.
13. The CPU cache management system of claim 10, wherein said cache management logic is further operable to schedule said system reboot.
14. The CPU cache management system of claim 10, wherein said cache management logic is further operable to report actions taken and update cache configuration in said non-volatile memory.
15. The CPU cache management system of claim 10, wherein said non-volatile memory is an EEPROM.
16. A method for managing a computer system having an operating system comprising the steps of:
monitoring a cache element on a CPU for a cache error;
recording cache error information upon occurrence of said cache error in a non-volatile memory;
determining whether said cache element is faulty based on said cache error information;
storing cache element repair information and CPU serial number in said non-volatile memory;
generating a system reboot;
reading a CPU serial number from said CPU;
comparing the read CPU serial number with the stored CPU serial number;
reading burned cache fuse data from said CPU if the stored CPU serial number does not match the read CPU serial number;
storing said read burned cache fuse data into said non-volatile memory if the stored CPU serial number does not match the read CPU serial number;
reading said cache configuration and from said non-volatile memory;
determining if a spare cache element is available if said cache element is faulty during said system reboot;
swapping in said spare cache element if said spare cache element is available and said cache element is faculty during said system reboot; and
updating cache configuration in said non-volatile memory.
17. The method of claim 16, wherein said cache element is determined to be faulty if a total number of errors occurring from said cache element exceeds a predetermined threshold.
18. The method of claim 17, wherein said predetermined threshold is based on a total number of errors occurring from said cache element over a predetermined time period.
19. The method of claim 16, wherein said monitoring step is performed by cache management logic within said operating system.
20. The method of claim 16, further comprising the step of: de-allocating said at least one CPU if said at least one spare cache element is not available.
21. The method of claim 20, further comprising the steps of: determining whether a spare CPU is available; and swapping in said spare CPU for said de-allocated CPU if said spare CPU is available.
22. The method of claim 16, wherein said non-volatile memory is an EEPROM.
23. A processor comprising:
a plurality of first memory portions;
a plurality of second memory portions;
a non-volatile memory on said processor;
logic for determining whether a first memory portion is faulty;
logic for storing memory portion error information, repair information, a processor serial number, and configuration in said non-volatile memory; and
logic for replacing the faulty first memory portion with a second memory portion during a system reboot;
logic for reading a processor serial number from said processor;
logic for comparing the read processor serial number with the stored processor serial number; and
logic for clearing said repair information and said cache configuration from said non-volatile memory if the stored processor serial number does not match the read processor serial number.
24. The processor of claim 23 wherein the logic for determining whether a first memory portion is faulty comprises logic for monitoring errors associated the first memory portion.
25. The processor of claim 23 wherein the logic for determining whether a first memory portion is faulty comprises logic for comparing a number of errors associated with the first memory portion to a threshold value.
26. The processor of claim 23 wherein the logic for replacing the faulty first memory portion with a second memory portion comprises logic for determining if a second memory portion is available for use in the replacement.
27. The processor of claim 23 wherein the logic for replacing the faulty first memory portion with a second memory portion comprises logic for de-allocating the processor if a second memory portion is not available for use in the replacement.
28. The processor of claim 23, wherein said non-volatile memory is an EEPROM.
29. A processor comprising:
a first cache means configured for high-speed information storage and retrieval from the processor;
a second cache means for high-speed information storage and retrieval;
a non-volatile memory on said processor;
means for determining whether any portion of the first cache means configured for high-speed information storage is faulty;
means for storing cache error information, repair information, a processor serial number, and cache configuration in said non-volatile memory; and
means for replacing the faulty portion of the first cache means with at least a portion of the second cache means for high-speed information storage and retrieval during a system reboot;
means for reading a serial number from said processor;
means for comparing the read processor serial number with the stored processor serial number; and
means for clearing repair information and said cache configuration from said non-volatile memory if the stored processor serial number does not match the read processor serial number.
30. The processor of claim 29, wherein the means for determining comprises means for monitoring errors associated the first cache means.
31. The processor of claim 29, wherein the means for determining comprises means for comparing a number of errors associated with the first cache means to a threshold value.
32. The processor of claim 29, wherein the means for replacing comprises means for determining if any portion of the second cache means is available for use in the replacement.
33. The processor of claim 29, wherein the means for replacing comprises means for de-allocating the processor if no portion of the second cache means is available for use in the replacement.
34. The processor of claim 29, wherein said non-volatile memory is an EEPROM.
Patent Citations (42)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4684885(A) | 1987-08-01 | Chapman | Applicant |
| US5649090(A) | 1997-07-01 | Edwards | Applicant |
| US5954435(A) | 1999-09-01 | Yoshida | Applicant |
| US5961653(A) | 1999-10-01 | Kalter | Applicant |
| US6006311(A) | 1999-12-01 | Arimilli et al. | Examiner |
| US6181614(B1) | 2001-01-01 | Aipperspach et al. | Examiner |
| US6363506(B1) | 2002-03-01 | Karri | Applicant |
| US6425094(B1) | 2002-07-01 | Drogichen | Applicant |
| US6516429(B1) | 2003-02-01 | Bossen | Applicant |
| US6649090(B2) | 2003-11-01 | Funaki | Applicant |
| US6651182(B1) | 2003-11-01 | Chang et al. | Examiner |
| US6654707(B2) | 2003-11-01 | Wynn | Applicant |
| US6708294(B1) | 2004-03-01 | Nakao | Applicant |
| US6789048(B2) | 2004-09-01 | Arndt | Applicant |
| US6832329(B2) | 2004-12-01 | Ahrens et al. | Examiner |
| US6851071(B2) | 2005-02-01 | Bossen | Applicant |
| US6922798(B2) | 2005-07-01 | Nemani | Applicant |
| US6954851(B2) | 2005-10-01 | Natu | Applicant |
| US6973604(B2) | 2005-12-01 | Davis et al. | Examiner |
| US6985826(B2) | 2006-01-01 | Pomaranski | Applicant |
| US7007210(B2) | 2006-02-01 | Fields et al. | Examiner |
| US7047466(B2) | 2006-05-01 | Meaney et al. | Examiner |
| US7058782(B2) | 2006-06-01 | Henderson | Applicant |
| US7117388(B2) | 2006-10-01 | Arimilli | Applicant |
| US7134057(B1) | 2006-11-01 | Kaushik | Applicant |
| US7155637(B2) | 2006-12-01 | Jarboe, Jr. | Applicant |
| US7321986(B2) | 2008-01-01 | Ash | Applicant |
| US7350119(B1) | 2008-03-01 | Zuraski et al. | Examiner |
| US7409600(B2) | 2008-08-01 | Azevedo et al. | Examiner |
| US7415644(B2) | 2008-08-01 | Bower, III | Applicant |
| US7418367(B2) | 2008-08-01 | Pomaranski | Applicant |
| US7523349(B2) | 2009-04-01 | Barras | Applicant |
| US2003/0074598(A1) | 2003-04-01 | Bossen et al. | Examiner |
| US2003/0212884(A1) | 2003-11-01 | Lee | Applicant |
| US2004/0133826(A1) | 2004-07-01 | Zhu et al. | Examiner |
| US2004/0143776(A1) | 2004-07-01 | Cox | Applicant |
| US2004/0221193(A1) | 2004-11-01 | Armstrong | Applicant |
| US2005/0096875(A1) | 2005-05-01 | Pomaranski | Applicant |
| US2006/0080572(A1) | 2006-04-01 | Fong | Applicant |
| US2006/0248394(A1) | 2006-11-01 | McGowan | Applicant |
| US2008/0235454(A1) | 2008-09-01 | Duron | Applicant |
| US2008/0263394(A1) | 2008-10-01 | Tanabe | Applicant |
Non-Patent Literature (20)
- Final Office Action for U.S. Appl. No. 11/357,756 dated Mar. 27, 2009 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/357,756 dated Sep. 25, 2008 in the United States.Applicant
- Final Office Action for U.S. Appl. No. 11/356,521 dated Jan. 29, 2009 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/356,521 dated Sep. 23, 2008 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/357,396 dated Sep. 23, 2008 in the United States.Applicant
- Notice of Allowance for U.S. Appl. No. 11/356,560 dated Dec. 19, 2008 in the United States.Applicant
- Notice of Allowance for U.S. Appl. No. 11/356,560 dated Sep. 26, 2008 in the United States.Applicant
- Final Office Action for U.S. Appl. No. 11/356,548 dated Jan. 27, 2009 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/356,548 dated Jun. 25, 2008 in the United States.Applicant
- Final Office Action for U.S. Appl. No. 11/357,386 dated May 28, 2009 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/357,386 dated Dec. 19, 2008 in the United States.Applicant
- Final Office Action for U.S. Appl. No. 11/357,386 dated Sep. 9, 2008 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/357,386 dated Jun. 24, 2008 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/357,385 dated Apr. 16, 2009 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/357,385 dated Sep. 25, 2008 in the United States.Applicant
- Final Office Action for U.S. Appl. No. 11/356,559 dated Nov. 4, 2008 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/356,559 dated Jun. 30, 2008 in the United States.Applicant
- Notice Of Allowance for U.S. Appl. No. 11/356,564 dated Jan. 30, 2009 in the United States.Applicant
- Final Office Action for U.S. Appl. No. 11/356,564 dated Nov. 4, 2008 in the United States.Applicant
- Office Action for U.S. Appl. No. 11/356,564 dated Jun. 24, 2008 in the United States.Applicant