mem: Add a generic id field to the packet trace

This patch adds an optional generic 64-bit identifier field to the
packet trace. This can be used to store the sequential number of the
instruction that gave rise to the packet, thread id, master id,
"sub"-master within a larger module etc. As the field is optional it
has a marginal cost if not used.

1 files changed, 4 insertions, 1 deletions

diff --git a/src/proto/packet.proto b/src/proto/packet.proto
index 28c21ec40..957b494ab 100644
--- a/src/proto/packet.proto
+++ b/src/proto/packet.proto
@@ -52,11 +52,14 @@ message PacketHeader {
 // 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.
+// 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.
 message Packet {
   required uint64 tick = 1;
   required uint32 cmd = 2;
   required uint64 addr = 3;
   required uint32 size = 4;
   optional uint32 flags = 5;
+  optional uint64 id = 6;
 }