Source: http://www.google.com/patents/US8078801?dq=inassignee:Temic
Timestamp: 2014-03-16 14:50:27
Document Index: 677405595

Matched Legal Cases: ['Application No. 07254933', 'Application No. 07254933', 'Application No. 07254933', 'Application No. 07', 'Application No. 07253418', 'Application No. 10', 'Application No. 200680038567', 'Application No. 200710303558', 'Application No. 200710101675', 'Application No. 200710101675', 'Application No. 07253418', 'Application No. 102007006190', 'Application No. 102007006190', 'Application No. 102007006190', 'Application No. 112006002908', 'Application No. 112006002908', 'Application No. 2007', 'Application No. 2008', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 96104443', 'Application No. 200710101675', 'Application No. 96104443']

Patent US8078801 - Obscuring memory access patterns - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsFor each memory location in a set of memory locations associated with a thread, setting an indication associated with the memory location to request a signal if data from the memory location is evicted from a cache; and in response to the signal, reloading the set of memory locations into the cache....http://www.google.com/patents/US8078801?utm_source=gb-gplus-sharePatent US8078801 - Obscuring memory access patternsAdvanced Patent SearchPublication numberUS8078801 B2Publication typeGrantApplication numberUS 12/562,041Publication dateDec 13, 2011Filing dateSep 17, 2009Priority dateDec 27, 2006Also published asCN101231621A, CN101231621B, DE602007007566D1, EP1939752A1, EP1939752B1, US7610448, US20080162816, US20100299479Publication number12562041, 562041, US 8078801 B2, US 8078801B2, US-B2-8078801, US8078801 B2, US8078801B2InventorsMark Buxton, Ernie Brickell, Quinn A. Jacobson, Hong Wang, Baiju PatelOriginal AssigneeIntel CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (59), Non-Patent Citations (59), Referenced by (1), Classifications (18), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetObscuring memory access patternsUS 8078801 B2Abstract For each memory location in a set of memory locations associated with a thread, setting an indication associated with the memory location to request a signal if data from the memory location is evicted from a cache; and in response to the signal, reloading the set of memory locations into the cache.
setting an indication associated with a memory location to request a signal for each memory location in a set of memory locations associated with a thread, when data from the memory location is evicted from a cache; and
reloading the set of memory locations into the cache, in response to the signal, in at least one of:
a random order; and
a predetermined order.
2. The method of claim 1, wherein the signal further comprises an interrupt, and wherein the method further comprises registering a handler to respond to the signal.
3. The method of claim 1, wherein the set of memory locations further comprises a set of memory locations having data, at least in part, private to the thread.
4. The method of claim 1, wherein the signal comprises an interrupt.
5. The method of claim 4, wherein reloading the set of memory locations into the cache further comprises a handler reloading the set of memory locations into the cache in at least one of:
6. The method of claim 1, wherein setting the indication associated with the memory location further comprises:
setting an attribute bit, associated with a cache line of the data from the memory location, to a predetermined value, wherein the method further comprises logic of a processor for detecting the eviction of data from the memory location from the cache and generating the interrupt.
detecting that the thread has resumed execution following a context switch; and
reloading the set of memory locations into the cache at least in part in response to the detecting.
a memory communicatively coupled with the processor, the memory further comprising a program thread (thread),
wherein for each memory location in a set of memory locations associated with the thread, the thread is to set an indication associated with the memory location to request a signal when data from the memory location is evicted from a cache, and wherein, in response to the signal, the processor to reload the set of memory locations into the cache in at least one of:
9. The system of claim 8, wherein the thread is further operable to load the set of memory locations into the cache in at least one of:
10. The system of claim 9, wherein the signal comprises an interrupt.
11. The system of claim 10, wherein reloading the set of memory locations into the cache further comprises a handler reloading the set of memory locations into the cache in at least one of:
12. The system of claim 8, wherein the signal further comprises an interrupt, the thread is further operable to register a handler to respond to the signal.
13. The system of claim 12, wherein setting the indication associated with the memory location further comprises setting an attribute bit, associated with a cache line of the data from the memory location, to a predetermined value, and wherein the system further comprises logic to detect the eviction of data from the memory location from the cache and to generate the interrupt.
14. The system of claim 8, wherein the set of memory locations further comprises a set of memory locations having data, at least in part, private to the thread.
15. The system of claim 8, wherein the thread is further operable to detect that the thread has resumed execution following a context switch and to reload the set of memory locations into the cache at least in part in response to the detecting.
16. A tangible machine readable storage medium having stored thereon data that when accessed by a machine causes it to perform a method, the method comprising:
17. The tangible machine readable storage medium of claim 16, wherein the signal comprises an interrupt.
18. The tangible machine readable storage medium of claim 17, wherein reloading the set of memory locations into the cache further comprises a handler reloading the set of memory locations into the cache in at least one of:
19. The tangible machine readable storage medium of claim 16, wherein the signal further comprises an interrupt, wherein the method further comprises-registering a handler to respond to the signal.
20. The tangible machine readable storage medium of claim 19, wherein setting the indication associated with the memory location further comprises setting an attribute bit associated with the cache line of the data from the memory location to a predetermined value, the method further comprising logic of a processor for detecting the eviction of data from the memory location from the cache and generating the interrupt.
21. The tangible machine readable storage medium of claim 19, wherein the method further comprises:
22. The tangible machine readable storage medium of claim 16, wherein the set of memory locations further comprises a set of memory locations having data, at least in part, private to the thread.
CLAIM OF PRIORITY The present patent application claims priority to and incorporated by reference the corresponding U.S. patent application Ser. No. 11/646,642 entitled �OBSCURING MEMORY ACCESS PATTERNS�, filed on Dec. 27, 2006 and issued as U.S. Pat. No. 7,610,448 on Oct. 27, 2009.
CROSS-REFERENCE TO RELATED APPLICATION The present application is related to pending U.S. patent application Ser. No. 11/349,661 entitled �TECHNIQUE FOR USING MEMORY ATTRIBUTES,� filed on Feb. 7, 2006, and assigned to the assignee of the present invention; and to U.S. patent application Ser. No. 11/513,871 entitled �METHOD AND APPARATUS FOR PREVENTING SOFTWARE SIDE CHANNEL ATTACKS,� filed on Aug. 31, 2006, and assigned to the assignee of the present invention; and to U.S. patent application Ser. No. 11/254,286 entitled �TECHNIQUE FOR THREAD COMMUNICATION AND SYNCHRONIZATION,� filed on Oct. 19, 2005 and assigned to the assignee of the present invention.
BACKGROUND The access patterns of a program executing on a processor based system as the program accesses memory may inadvertently reveal private or sensitive information of the program. For example, the access patterns of an application encoding or decoding a secret cryptographic key may in some cases be used to determine the value of the bits in the key. Other exploits that use this type of information leakage may be readily envisaged.
In one specific instance, if two threads (also interchangeably termed �processes� in the context of this Application) executing on a processor based system share a cache memory (cache), it is possible for one thread, a �spy� thread, to observe information about the access patterns of the other thread, a �target� thread. This is because the access patterns of the target thread can cause data of the spy thread to be evicted from cache memory, and can thus alter the access time of the spy thread's access of memory.
Depending on different processor architectures in processor based systems, the spy thread may achieve this type of information leak detection either temporally or spatially. In the temporal case, the spy thread and the target thread may run on a single processor and be interleaved in execution, sharing the single processor's cache. In the spatial case, the spy thread and target thread may run on different processors of a multi-processor system, or on different cores of a multi-core processor, but the spy thread may still achieve this type of detection if the two processors or cores share a common cache.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 depicts a cache memory in an embodiment.
FIGS. 2 a and 2 b depict the flow of processing in one embodiment.
FIG. 3 depicts a processor based system in one embodiment.
DETAILED DESCRIPTION In one embodiment of the invention, memory attributes, (implemented, for example, as described in U.S. patent application Ser. No. 11/349,661 by Quinn et al., listed in the list of Cross Referenced Related Applications above), and associated with a particular segment, or �block�, of memory may be used indicate various properties of the memory block. For example, in one embodiment, there are associated with each block of memory attribute bits that may be defined by a user to indicate any number of properties of the memory block with which they are associated, such as access rights. In one embodiment, each block of memory may correspond to a particular cache line, such as a cache line within a level one (L1) or level two (L2) cache memory, and the attributes are represented with bit storage locations located with or otherwise associated with a cache line. In other embodiments, a block of memory for which attributes may be associated may be a size larger or smaller than a cache line.
FIG. 1 illustrates a portion of a cache memory, each cache line of which has an associated group of attribute bit storage locations, according to one embodiment of the invention. In particular, FIG. 1 illustrates a cache memory 100 including a cache line 105, which corresponds to a particular block of memory (not shown). The cache line 105 has associated therewith a number of attributes to be stored in the form of bits within storage location 110. Within the storage location 110 is a group of attribute bits 115 associated with cache line 105, which can store bits to represent various properties of the cache line, which can be used by a program executing on a processor based system that accesses the cache line.
In the embodiment illustrated in FIG. 1, the group of attribute bits contains four bits, which may represent one or more properties of the cache line, depending upon how the attribute bits are assigned. For example, in one embodiment, the attribute bits indicate that the program has recently checked that the block of memory is appropriate for the current portion of the program to access. In other embodiments, the attribute bits may indicate that the program has recorded a recent reference to this block of memory for later analysis by a performance monitoring tools, for example. In other embodiments, the attribute bits may designate other permissions, properties, etc.
In addition to the attribute bits, each line of cache may also have associated therewith a state value stored in state storage location 120. For example, in one embodiment the state storage location 120 contain state bits 125 associated with cache line 105 which designates whether the cache line is in a modified state, exclusively owned state, shared state, or invalid state. The state value can control whether various software threads, cores, or processors can use and/or modify information stored in the particular cache line. In some embodiments the state value is included in the attribute bits 115 for cache line 105.
In one embodiment of the invention, attributes associated with a block of memory may be accessed, modified, and otherwise controlled by specific operations, such as an instruction or micro-operation decoded from an instruction. For example, in one embodiment an instruction that both loads information from a cache line and sets the corresponding attribute bits (e.g., a �LOAD_SET� instruction) may be used. In other embodiments, an instruction that loads information from a cache line and checks the corresponding attribute bits (e.g., a �LOAD_CHECK� instruction) may be used in addition to a LOAD_SET instruction.
In still other embodiments, other instructions may be used to both control the attribute bits and access the corresponding cache data. For example, in one embodiment an instruction may be used that stores information to a cache line while either checking or setting (or both) the corresponding attribute bits (e.g., a �STORE_SET� and/or �STORE_CHECK� instruction). In some embodiments, instructions may be used to control or access the attribute bits that do not have an associated cache memory operation, such as load or store. For example, a �CLEAR_MAT� instruction that clears all attribute bits at a specified position (e.g. the third attribute bit for every line in the cache).
In the case of an instruction that checks the attributes associated with a cache line, one or more architectural scenarios within one or more processors or cores of a processor may be defined to perform certain events based on the attributes that are checked. There may be other types of events that can be performed in response to the attribute check. For example, in one embodiment, an architectural scenario may be defined to compare the attribute bits to a particular set of data and invoke an event based on the outcome of the compare. The event may, among other things, call a service routine which performs various operations in response to the scenario outcome before returning control to a thread or other process running in the system.
For example, one scenario that may be defined is one that invokes an event and corresponding handler upon detecting an Unexpected Memory State (UMS scenario). This may be useful if a thread or other process attempts to access a cache line expecting it to have a certain state, based on the attribute bits of the line, and instead the cache line is in another memory state, indicating that the cache line may no longer be associated with that particular thread or process. Another scenario that may be defined is one that invokes an event and corresponding handler upon detecting an invalidation of a cache line, either explicitly by a thread attempting to get ownership of the cache line in order to modify the content of the line or because the line got evicted by the cache management system in order to make room for other memory locations to be cached. This scenario is called the Memory Line Invalidate (MLI) scenario. This scenario may be useful for a thread to detect when a cache line previously allocated to a memory location of the thread has been evicted from the cache by a different thread. In some embodiments, other scenarios may be defined based on a check of cache line memory attributes. In other embodiments memory attributes of locations of finer granularity than the cache line may also be checked.
In one embodiment, functionality such as that described above or the equivalent may be used to obscure memory access patterns of a secure program or thread. In this embodiment, as depicted in FIG. 2 a, a thread first identifies all memory locations or blocks of interest. These are termed �critical� memory locations because they may be critical to the security of the thread or to the secrecy of a the keys involved in an decryption or encryption process. However, any set of memory locations may be identified by a thread for any purpose. The exact method of identification of these memory locations depends on the purpose and implementation of the program of which the thread is a part, and is beyond the scope of this disclosure. When using this technology to protect the cryptographic algorithm, AES, from cache side channel attacks, the program would indicate the s-Box tables as the critical memory locations, since the access to these tables is dependent upon the secret key.
Once the set of memory locations or blocks is identified, and the thread begins execution at 200, it first registers a handler at 210 to respond to a Memory Line Invalidate (MLI) scenario in this embodiment. The thread then loads all the critical memory locations into the cache, 220, using a LOAD_SET or a similar instruction to set an attribute bit in association with each cache line into which a critical memory location is loaded. There are two methods for using this attribute set. In one embodiment, the attribute bit selected is set to indicate to the underlying processor or processor core that its logic should respond to an MLI scenario for that cache line. That is, in this instance, the invalidation of a cache line so marked will cause an event to be generated that results in the invocation of the thread's registered handler by the processor or processor core. In another embodiment, whenever a LOAD_CHECK instruction is executed, the processor checks that the attribute bit is set. If it is, then execution follows as normal. If it is not set, then a handler is called to reload all of the critical memory locations into the cache using a LOAD_SET or similar instruction.
The actual load of the critical memory locations at 220 by the thread is performed in a random or a predefined arbitrary order that is preferably unrelated to the actual order in which the memory locations are to be accessed by the thread. This is to prevent any type of information leakage relating to the order of cache loading from being useful to a spy thread that may be able to observe the order in which the cache is loaded.
The thread then begins the actual work, 230, that is to be performed with the memory locations. As indicated earlier, the exact work done by the thread may vary, depending on its purpose, and may include various types of cryptographic functionality involving the critical memory locations, or other actions that require secrecy and security from information leakage, among many other types of functionality. This process continues as long as more work remains to be accomplished, 240, and the thread then terminates 250.
If during the execution of the thread following the load of the critical memory locations at 220, an outside asynchronous event causes an eviction of any of the lines of the cache for which the attribute bit has been set by the thread, an MLI scenario is invoked at 260. This causes the logic of the underlying processor or core to transfer control to the handler previously registered by the thread at 210. The main function of the handler is to prevent a spy thread from using the cache walk technique described above or a similar technique to detect the memory access patterns of the thread. In this embodiment, this is accomplished by re-loading the critical memory locations of the thread in some arbitrary order or in some random order at 280. The handler then terminates, returning control to the thread sequencer. Thus, any previous attempt by a spy thread to pre-load the cache with its data and then observe the cache line loading pattern of the target thread that is performing a private function may be thwarted. This is because any attempt by the spy thread to displace any of the cache lines containing critical memory locations will cause all the lines to be re-installed in the cache, thus obscuring the actual access patterns of the target thread.
Further processing may be required if critical data is evicted from the cache when a thread is not executing because of a context switch. In one embodiment, for which additional processing is depicted in FIG. 2 b, a mechanism may be used by a thread to detect that it has been context switched (one such mechanism is described in U.S. patent application Ser. No. 11/513,871 referenced above in the list of Cross-Referenced Related Applications, by McKeen, et al.). If a thread returns after a context switch, 205 and then the process detects that it has been context switched, 207, it may then check to see if any critical data was evicted during the time the thread was not executing, 215. If any data was evicted, the process may then perform a LOAD_SET on all of the critical data in its set, 225, and then continue execution. In some instances, a process may bypass the detection of data evictions at 215 and reload all critical memory locations into cache as at 225 after each context switch by default.
It should be understood that the processing in FIGS. 2 a and 2 b may coexist in an embodiment, thus allowing detection of data eviction during thread execution as in FIG. 2 a, while also handling the possibility of data eviction during thread context switches, as in FIG. 2 b. In another embodiment for handling a context switch, all of the data access of the critical data is done with a LOAD_CHECK instruction. The MLI method may also be used. Then after a context switch, as soon as one LOAD is performed that accesses a cache line that was evicted when the process was not executing, all the critical data will be loaded. In another embodiment, if the processor detects that there might have been a context switch, the processor may use a CLEAR_MAT or analogous instruction to clear all of memory attributes. In this way, no matter which data element is accessed after a context switch, the LOAD_CHECK instruction will trigger the handler to perform the LOAD_SET on all of the critical data in the set for the thread.
In other embodiments, many variations of the above described flow may occur. For example, the sequence of actions described as being executed by a handler thread (software) may alternatively be executed by logic of a processor or processor core in hardware. The exact nature of the attributes associated with cache lines may vary, for example in some embodiments only an attribute bit corresponding to the Memory Line Invalidate scenario may be present, and other attributes may or may not be present. Furthermore, attributes may be recorded as additional bits associated directly with lines in the cache, or in a separate register or other specialized memory. An MLI scenario may cause additional actions such as a logging action or a counter increment, among many others. The actual work performed by the handler that seeks to be protected may vary depending on its specific purpose. The manner of loading the critical memory locations into the cache may be different in the thread and the MLI scenario handler. Not all memory locations involved in a cryptographic operation may be deemed critical, and not all critical locations may have their attribute bit set in the cache in other embodiments. Many other variations are possible.
FIG. 3 illustrates a front-side-bus (FSB) computer system in which one embodiment of the invention may be used. A processor 305 accesses data from a level one (L1) cache memory 310 and main memory 315. In other embodiments of the invention, the cache memory may be a level two (L2) cache or other memory within a computer system memory hierarchy. Furthermore, in some embodiments, the computer system of FIG. 3 may contain both a L1 cache and an L2 cache.
Illustrated within the processor of FIG. 3 is a storage area 306 for machine state. In one embodiment storage area may be a set of registers, whereas in other embodiments the storage area may be other memory structures. The processor may have any number of processing cores. Other embodiments of the invention, however, may be implemented within other devices within the system, such as a separate bus agent, or distributed throughout the system in hardware, software, or some combination thereof.
The main memory 315 may be implemented in various memory sources, such as dynamic random-access memory (DRAM), a hard disk drive (HDD) 320, or a memory source located remotely from the computer system via network interface 330 containing various storage devices and technologies. The cache memory may be located either within the processor or in close proximity to the processor, such as on the processor's local bus 307.
Furthermore, the cache memory may contain relatively fast memory cells, such as a six-transistor (6T) cell, or other memory cell of approximately equal or faster access speed. The computer system of FIG. 3 may be a point-to-point (PtP) network of bus agents, such as microprocessors, that communicate via bus signals dedicated to each agent on the PtP network.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the description, terms such as �executing� or �processing� or �computing� or �calculating� or �determining� or the like, may refer to the action and processes of a processor-based system, or similar electronic computing device, that manipulates and transforms data represented as physical quantities within the processor-based system's storage into other data similarly represented or other such information storage, transmission or display devices.
Further, a design of an embodiment that is implemented in a processor may go through various stages, from creation to simulation to fabrication. Data representing a design may represent the design in a number of manners. First, as is useful in simulations, the hardware may be represented using a hardware description language or another functional description language. Additionally, a circuit level model with logic and/or transistor gates may be produced at some stages of the design process. Furthermore, most designs, at some stage, reach a level of data representing the physical placement of various devices in the hardware model. In the case where conventional semiconductor fabrication techniques are used, data representing a hardware model may be the data specifying the presence or absence of various features on different mask layers for masks used to produce the integrated circuit. In any representation of the design, the data may be stored in any form of a machine-readable medium. An optical or electrical wave modulated or otherwise generated to transmit such information, a memory, or a magnetic or optical storage such as a disc may be the machine readable medium. Any of these mediums may �carry� or �indicate� the design or software information. When an electrical carrier wave indicating or carrying the code or design is transmitted, to the extent that copying, buffering, or re-transmission of the electrical signal is performed, a new copy is made. Thus, a communication provider or a network provider may make copies of an article (a carrier wave) that constitute or represent an embodiment.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5202998Aug 31, 1990Apr 13, 1993International Business Machines CorporationFast, simultaneous multi-processor system status communication interfaceUS5428761 *Mar 12, 1992Jun 27, 1995Digital Equipment CorporationSystem for achieving atomic non-sequential multi-word operations in shared memoryUS5555398Apr 15, 1994Sep 10, 1996Intel CorporationWrite back cache coherency module for systems with a write through cache supporting busUS5909698Mar 17, 1997Jun 1, 1999International Business Machines CorporationCache block store instruction operations where cache coherency is achieved without writing all the way back to main memoryUS5974438 *Dec 31, 1996Oct 26, 1999Compaq Computer CorporationScoreboard for cached multi-thread processesUS5974507Apr 14, 1997Oct 26, 1999International Business Machines CorporationOptimizing a cache eviction mechanism by selectively introducing different levels of randomness into a replacement algorithmUS6026471 *Nov 19, 1996Feb 15, 2000International Business Machines CorporationAnticipating cache memory loader and methodUS6094729Dec 17, 1997Jul 25, 2000Advanced Micro Devices, Inc.Debug interface including a compact trace record storageUS6157986Dec 16, 1997Dec 5, 2000Advanced Micro Devices, Inc.Fast linear tag validation unit for use in microprocessorUS6189112Apr 30, 1998Feb 13, 2001International Business Machines CorporationTransparent processor sparingUS6295580Jan 27, 1998Sep 25, 2001Sgs-Thomson Microelectronics LimitedCache system for concurrent processesUS6332181May 4, 1998Dec 18, 2001International Business Machines CorporationRecovery mechanism for L1 data cache parity errorsUS6366946Dec 16, 1998Apr 2, 2002Microsoft CorporationCritical code processing managementUS6412056Oct 1, 1997Jun 25, 2002Compac Information Technologies Group, LpExtended translation lookaside buffer with fine-grain state bitsUS6480936 *Nov 20, 1998Nov 12, 2002Fujitsu LimitedStoring apparatus having a dynamic buffer for random or sequential accessUS6748496Apr 18, 2000Jun 8, 2004Ati International SrlMethod and apparatus for providing cacheable data to a peripheral deviceUS6854039Dec 5, 2001Feb 8, 2005Advanced Micro Devices, Inc.Memory management system and method providing increased memory access securityUS7114036Jan 14, 2004Sep 26, 2006International Business Machines CorporationMethod and apparatus for autonomically moving cache entries to dedicated storage when false cache line sharing is detectedUS7287126Jul 30, 2003Oct 23, 2007Intel CorporationMethods and apparatus for maintaining cache coherencyUS7392352Jul 7, 2005Jun 24, 2008Massachusetts Institute Of TechnologyComputer architecture for shared memory accessUS7496716 *Jul 18, 2006Feb 24, 2009Sun Microsystems, Inc.Methods and apparatus to implement parallel transactionsUS7610448 *Dec 27, 2006Oct 27, 2009Intel CorporationObscuring memory access patternsUS7624236Dec 27, 2004Nov 24, 2009Intel CorporationPredictive early write-back of owned cache blocks in a shared memory computer systemUS20010025295Mar 9, 2001Sep 27, 2001International Business Machines CorporationComputer system, memory management method, storage medium and program transmission apparatusUS20020087815Dec 30, 2000Jul 4, 2002Arimilli Ravi KumarMicroprocessor reservation mechanism for a hashed address systemUS20030061452Sep 27, 2002Mar 27, 2003Kabushiki Kaisha ToshibaProcessor and method of arithmetic processing thereofUS20030097529Oct 16, 2001May 22, 2003International Business Machines Corp.High performance symmetric multiprocessing systems via super-coherent data mechanismsUS20030126379Dec 31, 2001Jul 3, 2003Shiv KaushikInstruction sequences for suspending execution of a thread until a specified memory access occursUS20030182571Mar 20, 2003Sep 25, 2003Kabushiki Kaisha ToshibaInternal memory type tamper resistant microprocessor with secret protection functionUS20030225976Jun 4, 2002Dec 4, 2003Erdem HokenekMethod and apparatus for multithreaded cache with simplified implementation of cache replacement policyUS20040162967Aug 8, 2003Aug 19, 2004Marc TremblayStart transactional execution (STE) instruction to support transactional program executionUS20040225849 *May 6, 2003Nov 11, 2004Wolczko Mario I.Method and apparatus for relocating objects within an object-addressed memory hierarchyUS20040255084Jun 12, 2003Dec 16, 2004International Business Machines CorporationShadow register to enhance lock acquisitionUS20040268094Feb 14, 2001Dec 30, 2004Mohammad AbdallahMethod and apparatus for floating point operations and format conversion operationsUS20050015562 *Jul 16, 2003Jan 20, 2005Microsoft CorporationBlock cache size management via virtual memory manager feedbackUS20050138306Dec 19, 2003Jun 23, 2005Panchbudhe Ankur P.Performance of operations on selected data in a storage areaUS20050198637Feb 26, 2004Sep 8, 2005Daniel KoganThread-based limitation on computer applicationUS20070043916Aug 16, 2005Feb 22, 2007Aguilar Maximino JrSystem and method for light weight task switching when a shared memory condition is signaledUS20070124543 *Nov 28, 2005May 31, 2007Sudhir DhawanApparatus, system, and method for externally invalidating an uncertain cache lineUS20070124546Nov 29, 2005May 31, 2007Anton BlanchardAutomatic yielding on lock contention for a multi-threaded processorUS20070169002Dec 15, 2005Jul 19, 2007International Business Machines CorporationProfile-driven lock handlingUS20070198781 *Jul 18, 2006Aug 23, 2007David DiceMethods and apparatus to implement parallel transactionsUS20070277001 *May 26, 2006Nov 29, 2007Mevergnies Michael Neve DeApparatus and method for reducing information leakage between processes sharing a cacheUS20090328053Sep 4, 2009Dec 31, 2009Sun Microsystems, Inc.Adaptive spin-then-block mutual exclusion in multi-threaded processingCN1659526AJun 3, 2003Aug 24, 2005杉桥技术公司Method and apparatus for multithreaded cache with cache eviction based on thread identifierDE10309919A1Mar 7, 2003Sep 23, 2004Infineon Technologies AgBuffer module for driving memory arrangements esp. for fast storage architecture, uses control unit for stopping writing of data from temporary write store to allow required data to be read via second data-interfaceEP1347384A2Mar 20, 2003Sep 24, 2003Kabushiki Kaisha ToshibaInternal memory type tamper resistant microprocessor with secret protection functionEP1939752A1Dec 18, 2007Jul 2, 2008Intel Corporation (a Delaware Corporation)Obscuring memory access patternsGB2434892A Title not availableGB2451003A Title not availableJP2001056783A Title not availableJP2002342163A Title not availableJP2003030049A Title not availableJPH10116192A Title not availableJPH11338772A Title not availableKR940015822A Title not availableWO2003054693A1Dec 12, 2001Jul 3, 2003Marcus DahlstroemCollision handling apparatus and methodWO2003102780A1Jun 3, 2003Dec 11, 2003Sandbridge Technologies IncMethod and apparatus for multithreaded cache with cache eviction based on thread identifierWO2007047959A1Oct 19, 2006Apr 26, 2007Intel CorpTechnique for thread communication and synchronization* Cited by examinerNon-Patent CitationsReference1 *Bonneau et al., "Cache-Collision Timing Attacks Against AES" from Cryptographic Hardware and Embedded Systems-CHES 2006 8th International Workshop, Oct. 2006.2 *Bonneau et al., "Cache-Collision Timing Attacks Against AES" from Cryptographic Hardware and Embedded Systems�CHES 2006 8th International Workshop, Oct. 2006.3Bracy et al., "Disintermediated Active Communication", IEEE Computer Architecture Letters, vol. 5, No. 2, Jul.-Dec. 2006, 4 pages.4EPO, "European Search Report", European Application No. 07254933.0, Dated May 28, 2008, 5 pages.5EPO, EP Office Action, European Application No. 07254933.0-1229 / 1939752, mailed Jan. 16, 2009, 6 pages.6EPO, European Application No. 07254933.0, Dated Jul. 7, 2008, 1 page.7EPO, European Patent Application No. 07 254 933.0-1229. Office Action issued on May 28, 2009, 5 pages.8Extended Search Report for European Patent Application No. 07253418.3 Mailed Feb. 12, 2008, 8 pages.9Fillo et al., "The M-Machine Multicomputer", Proceedings of the 28th International Symposium on Microarchitecture, Mar. 1995, 14 pages.10Final Office Action for Korean Patent Application No. 10-2008-7009297 Mailed Sep. 27, 2010, 3 pages.11Final Office Action for U.S. Appl. No. 11/349,661 Mailed Aug. 10, 2010, 20 pages.12Final Office Action for U.S. Appl. No. 11/513,871 Mailed Jan. 7, 2009, 8 pages.13Final Office Action for US Appl. No. 11/349,661 Mailed Jun. 23, 2009, 21 pages.14Final Office Action U.S. Appl. No. 11/254,286 Mailed Jul. 22, 2008, 12 pages.15Final Office Action U.S. Appl. No. 11/254,286 Mailed Mar. 10, 2010, 17 pages.16First Office Action for Chinese Patent Application No. 200680038567.1 Mailed Jan. 29, 2010, 10 pages.17First Office Action for Chinese Patent Application No. 200710303558.7; Mailed Mar. 4, 2010, 3 pages.18International Preliminary Report on Patentability for International Patent Application No. PCT/US2006/041094 Mailed Apr. 23, 2008, 8 pages.19International Search Report for International Patent Application No. PCT/US2006/041094 Mailed Mar. 9, 2007, 2 pages.20Non-Final Office Action and Search Report for United Kingdom Patent Application No. GB0702377.3 Mailed May 14, 2007, 7 pages.21Non-Final Office Action for China Patent Application No. 200710101675.5 Mailed Dec. 11, 2009, 17 pages.22Non-Final Office Action for China Patent Application No. 200710101675.5 Mailed Feb. 6, 2009, 8 pages.23Non-Final Office Action for European Patent Application No. 07253418.3Mailed Jun. 9, 2008, 2 pages.24Non-Final Office Action for German Patent Application No. 102007006190.2 Mailed Aug. 31, 2010, 13 pages.25Non-Final Office Action for German Patent Application No. 102007006190.2 Mailed Dec. 20, 2007, 18 pages.26Non-Final Office Action for German Patent Application No. 102007006190.2 Mailed Jun. 25, 2009, 15 pages.27Non-Final Office Action for German Patent Application No. 112006002908.8 Mailed Dec. 17, 2009, 4 pages.28Non-Final Office Action for German Patent Application No. 112006002908.8 Mailed Jul. 14, 2009, 8 pages.29Non-Final Office Action for Japanese Patent Application No. 2007-028172 Mailed May 25, 2010, with English translation, 5 pages.30Non-Final Office Action for Japanese Patent Application No. 2008-535803 Mailed Apr. 5, 2011, 4 pages.31Non-Final Office Action for Korean Patent Application No. 10-2007-12870 Mailed Apr. 28, 2008, with English Translation, 9 pages.32Non-Final Office Action for Korean Patent Application No. 10-2007-12870 Mailed Mar. 31, 2009, with English Translation, 5 pages.33Non-Final Office Action for Korean Patent Application No. 10-2008-7009297 Mailed Dec. 3, 2009, 7 pages.34Non-Final Office Action for Taiwan Patent Application No. 96104443 Mailed Mar. 11, 2010, 6 pages of Office Action including Search Report and 1 page of English Translation of Search Report.35Non-Final Office Action for U.S. Appl. No. 11/254,286 Mailed Aug. 27, 2007, 11 pages.36Non-Final Office Action for U.S. Appl. No. 11/254,286 Mailed Jun. 24, 2009, 13 pages.37Non-Final Office Action for U.S. Appl. No. 11/349,661 Mailed Jan. 4, 2010, 18 pages.38Non-Final Office Action for U.S. Appl. No. 11/349,661 Mailed Oct. 28, 2008, 17 pages.39Non-Final Office Action for U.S. Appl. No. 11/513,871 Mailed Aug. 20, 2008, 10 pages.40Non-Final Office Action for United Kingdom Patent Application No. GB0702377.3 Mailed Jul. 28, 2008, 5 pages.41Non-Final Office Action for United Kingdom Patent Application No. GB0702377.3 Mailed May 1, 2008, 5 pages.42Non-Final Office Action for United Kingdom Patent Application No. GB0808945.0 42P22024GB) Mailed May 27, 2010, 2 pages.43Non-Final Office Action for United Kingdom Patent Application No. GB0813998.2 Mailed Jun. 1, 2009, 4 pages.44Non-Final Office Action for United Kingdom Patent Application No. GB0813998.2 Mailed Nov. 6, 2008, 6 pages.45Non-Final Office Action U.S. Appl. No. 11/254,286 Mailed Sep. 8, 2010, 21 pages.46Notice of Allowance and Fees for U.S. Appl. No. 11/254,286 Mailed May 16, 2011, 8 pages.47Notice of Allowance and Fees for U.S.Appl. No. 11/646,642 Mailed Jun. 15, 2009, 12 Pages.48Notice of Allowance for China Patent Application No. 200710101675.5 Mailed Jun. 12, 2010, 9 pages.49Notice of Allowance for Taiwan Patent Application No. 96104443 Mailed Sep. 9, 2010, 3 pages.50Notice of Allowance for U.S. Appl. No. 11/349,661 Mailed Mar. 15, 2011, 18 pages.51Notice of Allowance for U.S. Appl. No. 11/513,871 Mailed May 6, 2009, 9 pages.52 *Osvik et al., "Cache Attacks and Countermeasures: The Case of AES" from Topics in Cryptology-CT-RSA 2006 The Cryptographers' Track at the RSA Conference 2006, Feb. 2005.53 *Osvik et al., "Cache Attacks and Countermeasures: The Case of AES" from Topics in Cryptology�CT�RSA 2006 The Cryptographers' Track at the RSA Conference 2006, Feb. 2005.54Page, D. "Partitioned Cache Architecture as a Side-Channel Defense Mechanism", Retrieved on Jan. 20, 2008 from http://citeseer.ist.psu.edu/chache/papers/cs2/433/http:zSzzSzeprint.iacr.orgzSz2005z Sz280.pdf/page05partitioned.pdf; Dep't of Computer Science, University of Bristol, Merchant Venturers Buildings, Woodland Road, Bristol.55 *Percival, Colin, "Cache Missing for Fun and Profit", Proc. of BSDCan 2005, http://www.daemonology.net/papers/cachemissing.pdf, (2005), 1-13.56Search Report for United Kingdom Patent Application No. GB0702377.3 Mailed Mar. 4, 2008, 3 pages.57 *The Apache Software Foundation, "Interface CachePolicy", http://www.jarvana.com/jarvana/view/org/apache/directory/server/apacheds-jdbm/1.5.6/apacheds-jdbm-1.5.6-javadoc.jarl/jdbm/helper/CachePolicy.html, Nov. 2003.58 *The Apache Software Foundation, "Interface CachePolicy<K,V>", http://www.jarvana.com/jarvana/view/org/apache/directory/server/apacheds-jdbm/1.5.6/apacheds-jdbm-1.5.6-javadoc.jarl/jdbm/helper/CachePolicy.html, Nov. 2003.59Written Opinion for International Patent Application No. PCT/US2006/041094 Mailed Apr., 2005, 7 pages.* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS8583872Aug 19, 2008Nov 12, 2013Fujitsu LimitedCache memory having sector functionClassifications U.S. Classification711/118, 711/133, 711/E12.069, 726/22, 711/144, 711/145International ClassificationG06F11/30, G06F12/12Cooperative ClassificationG06F21/78, G06F12/1458, G06F12/0842, G06F21/52, G06F9/30047European ClassificationG06F12/14D, G06F12/08B4T, G06F9/30A2P, G06F21/78, G06F21/52Legal EventsDateCodeEventDescriptionJun 2, 2011ASAssignmentFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUXTON, MARK;BRICKELL, ERNIE;JACOBSON, QUINN A.;AND OTHERS;SIGNING DATES FROM 20061222 TO 20070104;REEL/FRAME:026378/0711Owner name: INTEL CORPORATION, CALIFORNIARotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google