Hi All,
My group would also be interested in this feature, and have been discussing
something similar to Yan's suggestion.
Our use case would be for implementing architectural features of AArch64 which
require extensions to memory packets which are optional, or which would not be
applicable
This is to mimic systemc's protocol extension mechanism, where you can add
side channel info to a transaction. Sender state is more for keeping track
of information the sender needs related to a particular packet, rather than
to send additional state down the line to other consumers. For instance,
Hi Yan,
Can you use the Packet::pushSenderState(), popSenderState(), etc functions?
This is a stack instead of a linked-list, but it may work for your use
case. See
https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/src/mem/packet.hh#440
for more information.
The idea with that
Hi Gabe and everyone,
Thanks Gabe for bringing this up. Currently I am making a model in AXI
protocol and this model will need the AxUser and AxProt fields in the AXI
protocol. The packet in gem5 cannot carry additional information except the
actual read/write data. I think we can have the
