# US 2008/0307166 A1 · Store Handling in a Processor

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

- Number: US 2008/0307166 A1
- Document ID: US20080307166A1
- Status: Published application
- Kind: A1
- Application number: 11/758,303
- Filed: 2007-06-05
- Published: 2008-12-11
- Earliest claimed: 2007-06-05
- Assignees: Apple Inc.
- Inventors: Ramesh Gunna; Po-Yung Chang; Sudarshan Kadambi
- Web page: https://patentgrep.com/patent/US20080307166A1

## CPC

- G06F 12/0833: {in combination with broadcast means (e.g. for invalidation or updating)}
- G06F 9/3824: {Operand accessing}
- G06F 9/3834: {Maintaining memory consistency}
- G06F 9/3836: {Instruction issuing, e.g. dynamic instruction scheduling or out of order instruction execution}
- G06F 9/3867: {using instruction pipelines}
- G06F 12/1045: associated with a data cache
- G06F 12/0862: with prefetch
- G06F 2212/6028: Prefetching based on hints or prefetch instructions
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In one embodiment, a processor may be configured to write ECC granular stores into the data cache, while non-ECC granular stores may be merged with cache data in a memory request buffer. In one embodiment, a processor may be configured to detect that a victim block writeback hits one or more stores in a memory request buffer (or vice versa) and may convert the victim block writeback to a fill. In one embodiment, a processor may speculatively issue stores that are subsequent to a load from a load/store queue, but prevent the update for the stores in response to a snoop hit on the load.

## Claims

### Claim 1

A processor comprising:
a load/store unit comprising a queue, wherein the load/store unit is configured to issue a store memory operation from the queue;
a data cache coupled to the load/store unit;
a memory request buffer coupled to the load/store unit; and
a control unit configured to cause the issued store memory operation to write the data cache responsive to the issued store memory operation only updating one or more complete error correction code (ECC) granules, and wherein the control unit is configured to cause the issued store memory operation to be written to the memory request buffer responsive to the issued store operation partially updating at least one ECC granule.

### Claim 2 (depends on 1)

The processor as recited in claim 1 wherein the store data corresponding to the store memory operation and one or more ECC bits generated from the store data are written to the data cache.

### Claim 3 (depends on 1)

The processor as recited in claim 1 wherein the store data is merged, in the memory request buffer, with cache data read from the data cache.

### Claim 4 (depends on 3)

The processor as recited in claim 3 wherein one or more ECC bits are generated from the merged data in the memory request buffer.

### Claim 5 (depends on 4)

The processor as recited in claim 4 wherein the merged data and ECC bits are written from the memory request buffer to the data cache.

### Claim 6

A method comprising:
issuing a store memory operation from a queue;
writing a data cache responsive to the issued store memory operation only updating one or more complete error correction code (ECC) granules; and
writing the issued store memory operation to a memory request buffer responsive to the issued store operation partially updating at least one ECC granule.

### Claim 7 (depends on 6)

The method as recited in claim 6 wherein writing the data cache comprises writing the store data corresponding to the store memory operation and one or more ECC bits generated from the store data to the data cache.

### Claim 8 (depends on 6)

The method as recited in claim 6 further comprising merging, in the memory request buffer, store data corresponding to the store memory operation with cache data from the data cache.

### Claim 9 (depends on 8)

The method as recited in claim 8 further comprising generating one or more ECC bits from the merged data in the memory request buffer.

### Claim 10 (depends on 9)

The method as recited in claim 9 further comprising writing the merged data and ECC bits from the memory request buffer to the data cache.

### Claim 11

A processor comprising:
a pipeline comprising one or more stages between a load/store unit and one or more target locations of one or more store memory operations; and
the load store unit coupled to the pipeline, wherein the load/store unit comprises a load/store queue having an entry allocated to each pending load/store memory operation, wherein the load/store queue is coupled to receive a snoop address indicating a cache block that is to be updated by another device in a system with the processor, and wherein, responsive to detecting that the snoop address hits a load memory operation in the load/store queue and identifying a subsequent store memory operation in the load/store buffer that has been issued to the pipeline, the load/store unit is configured to prevent an update for the subsequent store memory operation in the pipeline at the target location of the subsequent store memory operation.

### Claim 12 (depends on 11)

The processor as recited in claim 11 wherein the subsequent store memory operation is subsequent to the load memory operation in program order.

### Claim 13 (depends on 11)

The processor as recited in claim 11 wherein one or more byte enables correspond to the subsequent store memory operation and identify one or more bytes in a byte range that are updated by store data corresponding to the subsequent store memory operation, and wherein the load/store unit is configured to prevent the update by causing the byte enables in the pipeline to be cleared.

### Claim 14 (depends on 13)

The processor as recited in claim 13 wherein the one or more target locations comprise a memory request buffer coupled to the pipeline, wherein the byte enables are cleared prior to or coincident with attempting to write the store data to the memory request buffer.

### Claim 15 (depends on 13)

The processor as recited in claim 13 wherein the one or more target locations comprise a data cache coupled to the pipeline, wherein the byte enables are cleared prior to or coincident with attempting to write the store data to the data cache.

### Claim 16 (depends on 11)

The processor as recited in claim 11 wherein the subsequent store memory operation is not hit by the snoop address.

### Claim 17

A method comprising:
receiving, in a processor, a snoop address indicating a cache block that is to be updated by another device in a system with the processor;
detecting that the snoop address hits a load memory operation in a load/store queue;
identifying a subsequent store memory operation in the load/store queue that has been issued to a pipeline between a load/store unit that includes the load/store queue and one or more target locations of one or more store memory operations; and
preventing an update for the subsequent store memory operation in the pipeline at the target location of the subsequent store memory operation responsive to the detecting and the identifying.

### Claim 18 (depends on 17)

The processor as recited in claim 17 wherein one or more byte enables correspond to the subsequent store memory operation and identify one or more bytes in a byte range that are updated by store data corresponding to the subsequent store memory operation, wherein preventing comprises clearing the byte enables in the pipeline.

### Claim 19 (depends on 18)

The method as recited in claim 18 wherein the one or more target locations comprise a memory request buffer coupled to the pipeline, wherein the clearing occurs prior to or coincident with attempting to write that store data to the memory request buffer.

### Claim 20 (depends on 18)

The method as recited in claim 18 wherein the one or more target locations comprise a data cache coupled to the pipeline, wherein the clearing occurs prior to or coincident with the attempting to writ the store data to the data cache.

### Claim 21 (depends on 17)

The method as recited in claim 17 wherein the subsequent store memory operation is not hit by the snoop address.
