[gem5-dev] Packet ID messages in the protobuf packet trace format

Hi folks. I'd like to propose adding a new type of message to the packet.proto format used for protobuf memory traces. Currently, packet IDs are opaque numbers which in some hand wavy way "identify" a packet, presumably to say where that packet came from (instruction, bus master, etc.) Currently

[gem5-dev] Change in public/gem5[master]: Add a LPDDR4 model (2133MHz, 4267MT/s, 2X16 configuration)

Xiaoyu Ma has uploaded this change for review. ( https://gem5-review.googlesource.com/4680 Change subject: Add a LPDDR4 model (2133MHz, 4267MT/s, 2X16 configuration) .. Add a LPDDR4 model (2133MHz, 4267MT/s, 2X16

[gem5-dev] Minor changes to gerrit review rules

Hi all, Currently, if there is a change to a patch on gerrit, all of the previous tags are cleared. For instance, if you upload a patch and receive a +2 review, then you make a minor update (or any update) the +2 is lost. I'm proposing changing this rule to only clear Maintainer +1 and keep all

[gem5-dev] Change in public/gem5[master]: tlm: Don't set SystemC time resolution

Matthias Jung has submitted this change and it was merged. ( https://gem5-review.googlesource.com/4520 ) Change subject: tlm: Don't set SystemC time resolution .. tlm: Don't set SystemC time resolution Some simulators

[gem5-dev] Cron <m5test@zizzer> /z/m5/regression/do-regression quick

*** gem5: ERROR: gem5 exited with non-zero status: 1* build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64i/simple-atomic: FAILED! * build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64i/simple-timing: FAILED! *