# US 2010/0169580 A1 · Memory model for hardware attributes within a transactional memory system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0169580 A1
- Document ID: US20100169580A1
- Status: Published application
- Kind: A1
- Application number: 12/346,539
- Filed: 2008-12-30
- Published: 2010-07-01
- Earliest claimed: 2008-12-30
- Assignees: Intel Corporation
- Inventors: Gad Sheaffer; Shlomo Raikin; Vadim Bassin; Ehud Cohen; Oleg Margulis
- Web page: https://patentgrep.com/patent/US20100169580A1

## CPC

- G06F 9/3834: {Maintaining memory consistency}
- G06F 9/30076: {to perform miscellaneous control operations, e.g. NOP}
- G06F 11/0715: {in a system implementing multitasking (multitasking per se G06F9/46)}
- G06F 11/0724: {in a multiprocessor or a multi-core unit (multiprocessors per se G06F15/80)}
- G06F 11/073: {in a memory management context, e.g. virtual memory or cache management (memory management G06F12/00; testing of static memory units G11C29/00)}
- G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)}
- G06F 11/3017: {where the computing system is implementing multitasking (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- G06F 11/3037: {where the computing system component is a memory, e.g. virtual memory, cache (accessing, addressing or allocating within memory systems or architectures G06F12/00; checking stores for correct operation G11C29/00)}
- G06F 11/3089: {Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents (software debugging using additional hardware using a specific debug interface G06F11/3656; performance evaluation by tracing or monitoring G06F11/3466)}
- G06F 11/3471: {Address tracing}
- G06F 12/0831: using a bus scheme, e.g. with bus monitoring or watching means
- G06F 12/084: with a shared cache
- G06F 9/3838: {Dependency mechanisms, e.g. register scoreboarding}
- G06F 2201/885: Monitoring specific for caches
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method and apparatus for providing a memory model for hardware attributes to support transactional execution is herein described. Upon encountering a load of a hardware attribute, such as a test monitor operation to load a read monitor, write monitor, or buffering attribute, a fault is issued in response to a loss field indicating the hardware attribute has been lost. Furthermore, dependency actions, such as blocking and forwarding, are provided for the attribute access operations based on address dependency and access type dependency. As a result, different scenarios for attribute loss and testing thereof are allowed and restricted in a memory model.

## Claims

### Claim 1

An apparatus comprising:
a data cache memory including a cache element to be associated with lossy data;
a loss field associated with the cache element; and
control logic coupled to the data cache memory and the loss field to update the loss field to hold a lossy value in response to determining the lossy data is to be lost.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the cache element includes a cache set.

### Claim 3 (depends on 2)

The apparatus of claim 2, wherein the loss field associated with the cache element comprises a loss bit within the data cache memory for the cache set, and wherein control logic to update the loss field to hold a lossy value includes the control logic to update the loss bit of a first logical value.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the cache element includes a cache entry of a cache set.

### Claim 5 (depends on 2)

The apparatus of claim 2, wherein the loss field associated with the cache element comprises a plurality of bits within the data cache memory for the cache set, wherein a bit of the plurality of bits is to be associated with the cache entry, and wherein control logic to update the loss field to hold a lossy value includes the control logic to update the bit of the plurality of bits to a first logical value.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the cache element to be associated with lossy data includes lossy hardware attributes associated with the cache element.

### Claim 7 (depends on 6)

The apparatus of claim 6, wherein lossy hardware attributes include hardware attributes selected from a group consisting of buffered hardware attributes, hardware attributes held in a state array associated with the cache memory, and hardware attributes held as lossy meta-data in the cache memory.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the control logic to update the loss field to hold a lossy value in response to determining the lossy data is to be lost comprises: the control logic selecting at least a portion of the data element for eviction to result in loss of the lossy data associated with the cache element.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein the control logic is further to initiate a fault of a subsequent load operation to read from the cache element in response to the loss field holding the lossy value.

### Claim 10

An apparatus comprising:
a cache memory including a cache element associated with an attribute;
a store buffer coupled to the cache memory to hold a store buffer entry associated with a store operation to update the attribute; and
control logic associated with the store buffer to block a subsequent load operation to read from the attribute until the attribute is updated in response to the store operation.

### Claim 11 (depends on 10)

The apparatus of claim 10, wherein the cache element is selected from a group consisting of a set of the cache memory, a line of the cache memory, and an entry of the cache memory.

### Claim 12 (depends on 11)

The apparatus of claim 11, wherein the cache element associated with the attribute comprises a coherency state entry corresponding to the cache element holding the attribute, and wherein the attribute includes a hardware monitor selected from a group consisting of a read monitor, a write monitor, and a buffering monitor.

### Claim 13 (depends on 10)

The apparatus of claim 10, wherein the attribute includes a read monitor attribute, and wherein the store operation includes a set the read monitor attribute instruction to update the read monitor attribute.

### Claim 14 (depends on 13)

The apparatus of claim 13, wherein the subsequent load operation includes a test the read monitor instruction is to read the read monitor attribute, test the read monitor instruction being subsequent in a program order to the set the read monitor attribute instruction.

### Claim 15

An apparatus comprising:
a plurality of hardware attributes associated with a cache element of a cache memory;
logic to determine if a dependency exists between a store operation to at least one of the plurality of hardware attributes and a subsequent load operation to at least one of the plurality of hardware attributes based at least on a first attribute access type of the store operation and a second attribute access type of the subsequent load operation; and
forwarding logic coupled to the logic, the forwarding logic to forward updated attribute data of the store operation to the subsequent load operation in response to determining the dependency exists between the store operation and the subsequent load operation.

### Claim 16 (depends on 15)

The apparatus of claim 15, wherein the logic to determine if a dependency exists between the store operation and the subsequent load operation based at least on the first attribute access type of the store operation and the second attribute access type of the subsequent load operation comprises: store buffer logic to hold the first attribute access type associated with the store operation, and dependency logic coupled to the store buffer logic to compare at least the first attribute access type and the second attribute access type.

### Claim 17 (depends on 16)

The apparatus of claim 16, wherein the first attribute access type and the second attribute access type are each individually selected from a read monitor access type, a write monitor access type, and a buffering access type.

### Claim 18 (depends on 16)

The apparatus of claim 16, wherein the store buffer logic to hold the first attribute access type associated with the store operation comprises store address buffer logic to hold the first attribute access type appended to a store address associated with the store operation, and wherein the dependency logic coupled to the store buffer logic and the forwarding logic is to compare at least the first attribute access type and the second attribute access type comprises the dependency logic to compare the first attribute access type appended to the store address and the second access type appended to a load address associated with the subsequent load.

### Claim 19 (depends on 18)

The apparatus of claim 18, further comprising snoop logic to snoop the store buffer in response to an external access request, wherein the forwarding logic is not to forward the updated attribute data in response to the external access request referencing the store address.

### Claim 20 (depends on 18)

The apparatus of claim 18, wherein the dependency logic is further to determine the dependency exists between the store operation and the subsequent load operation in response to the first attribute access type appended to the store address matching the second access type appended to the load address.

### Claim 21 (depends on 20)

The apparatus of claim 20, wherein the dependency logic is further to determine the dependency does not exist between the store operation and the subsequent load operation in response to the first attribute access type appended to the store address not matching the second access type appended to the load address, and wherein the forwarding logic is not to forward the updated attribute data in response to the dependency logic determining the dependency does not exist between the store operation and the subsequent load operation.

### Claim 22 (depends on 15)

The apparatus of claim 15, wherein the logic to determine if a dependency exists between the store operation and the subsequent load operation based at least on the first attribute access type of the store operation and the second attribute access type of the subsequent load operation comprises: store data buffer logic to hold the updated data in a position of a store data buffer entry associated with the store operation, wherein the position of the store data buffer entry represents the first attribute access type.

### Claim 23 (depends on 22)

The apparatus of claim 22, wherein the logic to determine if a dependency exists between the store operation and the subsequent load operation based at least on the first attribute access type of the store operation and the second attribute access type of the subsequent load operation further comprises: dependency logic coupled to the store data buffer and the forwarding logic to determine the dependency exists between the store operation and the subsequent load operation in response to a store address associated with the store operation matching a load address associated with the subsequent load operation and the second attribute access type being the same as the first attribute access type based on the position of the updated data held in the store data buffer entry.

### Claim 24 (depends on 23)

The apparatus of claim 23, wherein the dependency logic is to determine the dependency does not exist between the store operation and the subsequent load operation in response to the store address associated with the store operation note matching the load address associated with the subsequent load operation or the second attribute access type being the same as the first attribute access type based on the position of the updated attribute data held in the store data buffer entry, and wherein the forwarding logic is to not forward the updated attribute data in response to the dependency logic determining the dependency does not exist between the store operation and the subsequent load operation.

### Claim 25

A method comprising:
encountering a load operation to read a hardware attribute, the load operation being associated with an attribute type and referencing an address associated with a hardware attribute of the attribute type;
determining if an in-flight previous store operation is associated with the attribute type and references the address associated with the hardware attribute; and
performing a dependency action in response to determining the in-flight previous store operation is associated with the attribute type and references the address associated with the hardware attribute.

### Claim 26 (depends on 25)

The method of claim 25, wherein the load operation includes a test a hardware attribute operation, and wherein the in-flight previous store operation includes a set a hardware attribute operation.

### Claim 27 (depends on 25)

The method of claim 25, wherein the attribute type is selected from a group consisting of a read monitor attribute type, a write monitor attribute type, and a buffering attribute type.

### Claim 28 (depends on 25)

The method of claim 25, wherein determining if an in-flight previous store operation is associated with the attribute type and references the address associated with the hardware attribute comprises searching a store address buffer with a representation of the attribute type appended to the address and determining the in-flight previous store operation is associated with the attribute type and references the address associated with the hardware attribute in response to finding a store address buffer entry of the store address buffer holding the representation of the attribute type appended to the address.

### Claim 29 (depends on 25)

The method of claim 25, wherein determining if an in-flight previous store operation is associated with the attribute type and references the address associated with the hardware attribute comprises:
searching a store buffer for a store buffer entry associated with the address;
determining a position of store data associated with the hardware attribute held in a store buffer entry of the store buffer in response to finding the store buffer entry associated with the address;
determining a store attribute type based on the position of the store data held in the store buffer entry; and
determining the in-flight previous store operation is associated with the attribute type and references the address associated with the hardware attribute in response to determining the store attribute type is the same as the attribute type associated with the load operation.

### Claim 30 (depends on 25)

The method of claim 25, wherein performing a dependency action comprises forwarding store data associated with the in-flight previous store operation.

### Claim 31 (depends on 25)

The method of claim 25, wherein performing a dependency action comprises blocking the load operation until the hardware attribute is updated by the in-flight previous store operation.

### Claim 32 (depends on 25)

The method of claim 25, further comprising updating a loss field associated with the hardware attribute to a loss value in response to an eviction of a cache location associated with the hardware attribute, which is to result in loss of the hardware attribute.

### Claim 33 (depends on 32)

The method of claim 32, wherein the load operation is faulted in response to encountering the load operation to read the hardware attribute and the loss field holding the loss value.
