# US 2014/0156976 A1 · Method, apparatus and system for selective execution of a commit instruction

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

- Number: US 2014/0156976 A1
- Document ID: US20140156976A1
- Status: Published application
- Kind: A1
- Application number: 13/995,441
- Filed: 2011-12-22
- Published: 2014-06-05
- Earliest claimed: 2011-12-22
- Inventors: Enric Gibert Codina; Josep M. Codina; Fernando Latorre; Pedro Marcuello; Pedro Lopez; Crispin Gomez Requena; Antonio Gonzalez; Mirem Hyuseinova; Christos E. Kotselidis; Marc Lupon; Carlos Madriles Gimeno; Grigorios Magklis; Alejandro Martinez Vicente; Raul Martinez; Daniel Ortega; Demos Pavlou; Kyriakos A. Stavrou; Georgios Tournavitis; Polychronis Xekalakis
- Web page: https://patentgrep.com/patent/US20140156976A1

## CPC

- G06F 9/30145: {Instruction analysis, e.g. decoding, instruction word fields}
- G06F 9/30087: {Synchronisation or serialisation instructions}
- G06F 9/30185: {according to one or more bits in the instruction, e.g. prefix, sub-opcode}
- G06F 9/3842: {Speculative instruction execution}
- G06F 9/3854: {Instruction completion, e.g. retiring, committing or graduating}
- G06F 9/3858: {Result writeback, i.e. updating the architectural state or memory}
- G06F 9/3863: {using multiple copies of the architectural state, e.g. shadow registers}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques and mechanisms for a processor to determine whether a commit action is to be performed. In an embodiment, a processor performs operations to determine whether a commit instruction is for contingent performance of a commit action. In another embodiment, one or more conditions of processor state are evaluated in response to determining that the commit instruction is for contingent performance of the commit action, where the evaluation is performed to determine whether the commit action indicated by the commit instruction is to be performed.

## Claims

### Claim 1

A method at a processor, the method comprising:
detecting a commit instruction indicating a commit action;
in response to the detecting, determining whether the commit instruction is for contingent performance of the commit action; and
based on the determining, generating a signal indicating whether one or more conditions are to be evaluated for determining whether the commit action is to be performed.

### Claim 2 (depends on 1)

The method of claim 1, wherein determining whether the commit instruction is for contingent performance of the commit action is based on a value of a command contingency parameter of the command instruction.

### Claim 3 (depends on 1)

The method of claim 1, wherein determining whether the commit instruction is for contingent performance of the commit action is based on a command field of the commit instruction indicating a commit instruction type which is specific to contingent performance of commit actions.

### Claim 4 (depends on 1)

The method of claim 1, wherein the commit instruction includes a command field including information indicating an instruction type of the commit instruction, wherein determining whether the commit instruction is for contingent performance of the commit action includes identifying whether the commit instruction further includes a command contingency parameter.

### Claim 5 (depends on 1)

The method of claim 1, wherein the commit instruction is determined to be for contingent performance of the commit action, the method further comprising:
evaluating the one or more conditions to identify whether the commit action is to be performed, wherein the one or more conditions includes processor state which is independent of the commit instruction being received by the processor.

### Claim 6 (depends on 5)

The method of claim 5, wherein evaluating the one or more conditions is based on a count of a number of instructions executed since an event preceding the detecting the commit instruction.

### Claim 7 (depends on 6)

The method of claim 6, wherein the event includes one or a commit action and a rollback action.

### Claim 8 (depends on 5)

The method of claim 5, wherein evaluating the one or more conditions is based on a count of a number of memory requests awaiting global observation in the processor.

### Claim 9 (depends on 5)

The method of claim 5, wherein evaluating the one or more conditions is based on a number of pending interrupts.

### Claim 10 (depends on 1)

The method of claim 1, wherein the commit instruction of a commit instruction type which is generic to both categorical performance of commit actions commands and contingent performance of commit actions.

### Claim 11 (depends on 10)

The method of claim 10, wherein, according to configuration information of the processor, an instruction of the commit instruction type is presumed to represent a contingent commit command, in the absence of any command contingency parameter of the instruction specifying that the instruction represents a categorical commit command.

### Claim 12 (depends on 10)

The method of claim 10, wherein, according to configuration information of the processor, an instruction of the commit instruction type is presumed to represent a categorical commit command, in the absence of any command contingency parameter of the instruction specifying that the instruction represents a contingent commit command.

### Claim 13

A processor comprising:
an instruction set;
a decoder including circuit logic to detect a commit instruction indicating a commit action and to decode the commit instruction according to the instruction set; and
an execution unit to execute the decoded commit instruction;
wherein the decoder and the execution unit to determine whether the commit instruction is for contingent performance of the commit action, and wherein the decoder and the execution unit to generate, based on the determining, a signal indicating whether one or more conditions are to be evaluated for determining whether the commit action is to be performed.

### Claim 14 (depends on 13)

The processor of claim 13, wherein the decoder and the execution unit to determine whether the commit instruction is for contingent performance of the commit action is based on a value of a command contingency parameter of the command instruction.

### Claim 15 (depends on 13)

The processor of claim 13, wherein the decoder and the execution unit to determine whether the commit instruction is for contingent performance of the commit action is based on a command field of the commit instruction indicating a commit instruction type which is specific to contingent performance of commit actions.

### Claim 16 (depends on 13)

The processor of claim 13, wherein the commit instruction includes a command field including information indicating an instruction type of the commit instruction, wherein the decoder and the execution unit to determine whether the commit instruction is for contingent performance of the commit action includes identifying whether the commit instruction further includes a command contingency parameter.

### Claim 17 (depends on 13)

The processor of claim 13, wherein the decoder and the execution unit further to evaluate the one or more conditions to identify whether the commit action is to be performed, wherein the one or more conditions includes processor state which is independent of the commit instruction being received by the processor.

### Claim 18 (depends on 17)

The method of claim 17, wherein the evaluating the one or more conditions is based on a count of a number of instructions executed since an event preceding the detecting the commit instruction.

### Claim 19 (depends on 18)

The method of claim 18, wherein the event includes one or a commit action and a rollback action.

### Claim 20 (depends on 17)

The method of claim 17, wherein the evaluating the one or more conditions is based on a count of a number of memory requests awaiting global observation in the processor.

### Claim 21 (depends on 17)

The method of claim 17, wherein the evaluating the one or more conditions is based on a number of pending interrupts.

### Claim 22 (depends on 13)

The processor of claim 13, wherein the commit instruction of a commit instruction type which is generic to both categorical performance of commit actions commands and contingent performance of commit actions.

### Claim 23 (depends on 22)

The processor of claim 22, wherein, according to configuration information of the processor, an instruction of the commit instruction type is presumed to represent a contingent commit command, in the absence of any command contingency parameter of the instruction specifying that the instruction represents a categorical commit command.

### Claim 24 (depends on 22)

The processor of claim 22, wherein, according to configuration information of the processor, an instruction of the commit instruction type is presumed to represent a categorical commit command, in the absence of any command contingency parameter of the instruction specifying that the instruction represents a contingent commit command.

### Claim 25

A computer platform comprising:
a memory;
a processor coupled to the memory, the processor including
an instruction set;
a decoder coupled including circuit logic to detect a commit instruction indicating a commit action and to decode the commit instruction according to the instruction set; and
an execution unit to execute the decoded commit instruction;
wherein the decoder and the execution unit to determine whether the commit instruction is for contingent performance of the commit action, and wherein the decoder and the execution unit to generate, based on the determining, a signal indicating whether one or more conditions arc to be evaluated for determining whether the commit action is to be performed; and
a network interface to couple the computer platform to a network.

### Claim 26 (depends on 25)

The computer platform of claim 25, wherein the decoder and the execution unit to determine whether the commit instruction is for contingent performance of the commit action is based on a value of a command contingency parameter of the command instruction.

### Claim 27 (depends on 25)

The computer platform of claim 25, wherein the decoder and the execution unit to determine whether the commit instruction is for contingent performance of the commit action is based on a command field of the commit instruction indicating a commit instruction type which is specific to contingent performance of commit actions.

### Claim 28 (depends on 25)

The computer platform of claim 25, wherein the commit instruction includes a command field including information indicating an instruction type of the commit instruction, wherein the decoder and the execution unit to determine whether the commit instruction is for contingent performance of the commit action includes identifying whether the commit instruction further includes a command contingency parameter.

### Claim 29 (depends on 25)

The computer platform of claim 25, wherein the decoder and the execution unit further to evaluate the one or more conditions to identify whether the commit action is to be performed, wherein the one or more conditions includes processor state which is independent of the commit instruction being received by the processor.

### Claim 30 (depends on 29)

The method of claim 29, wherein the evaluating the one or more conditions is based on a count of a number of instructions executed since an event preceding the detecting the commit instruction.
