Re: [gem5-dev] Ruby failure

Hi Giacomo, How many CPUs/caches/directories are you trying to simulate? This looks like you might be hitting a limit on the number of simulated components (controllers/machines). Another possibility is that somehow the protocol is not constructing a machine id correctly. Did you make any

[gem5-dev] Ruby failure

Hi all, I am debugging a configuration error I get when I try to run ruby with a personal platform: gem5.debug: build/ARM_MOESI/mem/ruby/common/NetDest.cc:41: void NetDest::add(MachineID): Assertion `bitIndex(newElement.num) < m_bits[vecIndex(newElement)].getSize()' failed. I don't have any

[gem5-dev] Change in gem5/gem5[master]: syscall_emul: Different HWCAP for ArmProcess32/64

Hello Andreas Sandberg, I'd like you to do a code review. Please visit https://gem5-review.googlesource.com/c/public/gem5/+/12884 to review the following change. Change subject: syscall_emul: Different HWCAP for ArmProcess32/64

[gem5-dev] Change in gem5/gem5[master]: arch-x86: Add ACPI support for MADT

Maximilian Stein has uploaded this change for review. ( https://gem5-review.googlesource.com/c/public/gem5/+/12864 Change subject: arch-x86: Add ACPI support for MADT .. arch-x86: Add ACPI support for MADT This extends ACPI