package ProtoMessage

Get desktop application:
View/edit binary Protocol Buffers messages

• required uint64 pc = 1

• optional fixed32 inst = 2

  Either inst or inst_bytes must be used, but never both. That should be enforced by the oneof keyword, but that's not supported in all versions of protobuf syntax we need to work with for now.

• optional bytes inst_bytes = 9

• optional uint32 nodeid = 3

• optional uint32 cpuid = 4

• optional fixed64 tick = 5

• optional Inst.InstType type = 6

  add, mul, fp add, load, store, simd add, …

• optional uint32 inst_flags = 7

  Deprecated:

  execution mode information

• repeated Inst.MemAccess mem_access = 8

Used in: Inst

• None = 0

• IntAlu = 1

• IntMul = 2

• IntDiv = 3

• FloatAdd = 4

• FloatCmp = 5

• FloatCvt = 6

• FloatMult = 7

• FloatDiv = 8

• FloatSqrt = 9

• SIMDIntAdd = 10

• SIMDIntAddAcc = 11

• SIMDIntAlu = 12

• SIMDIntCmp = 13

• SIMDIntCvt = 14

• SIMDMisc = 15

• SIMDIntMult = 16

• SIMDIntMultAcc = 17

• SIMDIntShift = 18

• SIMDIntShiftAcc = 19

• SIMDSqrt = 20

• SIMDFloatAdd = 21

• SIMDFloatAlu = 22

• SIMDFloatCmp = 23

• SIMDFloatCvt = 24

• SIMDFloatDiv = 25

• SIMDFloatMisc = 26

• SIMDFloatMult = 27

• SIMDFloatMultAdd = 28

• SIMDFloatSqrt = 29

• MemRead = 30

• MemWrite = 31

• IprAccess = 32

• InstPrefetch = 33

If the operation does one or more memory accesses

Used in: Inst

• required uint64 addr = 1

• required uint32 size = 2

• optional uint32 mem_flags = 3

Packet to encapsulate an instruction in the o3cpu data dependency trace. The required fields include the instruction sequence number and the type of the record associated with the instruction e.g. load. The request related fields are optional, namely address, size and flags. The dependency related information includes a repeated field for order dependencies and register dependencies for loads, stores and comp records. There is a field for the computational delay with respect to the dependency that completed last. A weight field is used to account for committed instruction that were filtered out before writing the trace and is used to estimate ROB occupancy during replay. An optional field is provided for the instruction PC.

• required uint64 seq_num = 1

• required InstDepRecord.RecordType type = 2

• optional uint64 p_addr = 3

• optional uint32 size = 4

• optional uint32 flags = 5

• repeated uint64 rob_dep = 6

• required uint64 comp_delay = 7

• repeated uint64 reg_dep = 8

• optional uint32 weight = 9

• optional uint64 pc = 10

• optional uint64 v_addr = 11

• optional uint32 asid = 12

Used in: InstDepRecord

• INVALID = 0

• LOAD = 1

• STORE = 2

• COMP = 3

Packet header for the o3cpu data dependency trace. The header fields are the identifier describing what object captured the trace, the version of this file format, the tick frequency of the object and the window size used to limit the register dependencies during capture.

• required string obj_id = 1

• optional uint32 ver = 2

• required uint64 tick_freq = 3

• required uint32 window_size = 4

Packet header with the identifier describing what object captured the trace, the version of this file format, and the tick frequency for all the packet time stamps.

• required string obj_id = 1

• required uint32 ver = 2

• required uint64 tick_freq = 3

• required bool has_mem = 4

Each packet in the trace contains a tick (which can be translated to absolute time using the frequency in the header), the command, the address, and the size in bytes. The optional flags are used to capture the request flags that convey information about cacheability, if the packet is an instruction fetch or prefetch or not, etc. An optional id field is added for generic use to identify the packet or the "owner" of the packet. An example of the latter is the sequential id of an instruction, or the master id etc. An optional field for PC of the instruction for which this request is made is provided.

• required uint64 tick = 1

• required uint32 cmd = 2

• required uint64 addr = 3

• required uint32 size = 4

• optional uint32 flags = 5

• optional uint64 pkt_id = 6

• optional uint64 pc = 7

Packet header with the identifier describing what object captured the trace, the version of this file format, and the tick frequency for all the packet time stamps.

• required string obj_id = 1

• optional uint32 ver = 2

• required uint64 tick_freq = 3

• repeated PacketHeader.IdStringEntry id_strings = 4

This is supposed to be wire equivalent to the "map" construct supported by the proto3 version of the protobuf description syntax. When that becomes widely available, this should be converted over to use it.

Used in: PacketHeader

• optional uint32 key = 1

• optional string value = 2