Hello everyone, I’m an undergraduate student working on a project where I am to evaluate a hardware accelerator my PhD student is working on in a chiplet-based system. We are running garnet2.0, and it would be infeasible to port it to garnet3.0.
So far, I’ve had success configuring a chiplet configuration in Python and I’ve also been able to achieve a 1:n (n chiplets) memory to LLC mapping. Unfortunately, we found that there was deadlock under certain workloads. This led to the discovery that cache lines were not able to be shared across multiple chiplets (from memory -> cache). To simulate accurately, this is a requirement. I’ve been attempting to look into this issue, but I wanted to ask here for insight. I was able to find success with creating “cluster-private” LLC chiplets with built-in gem5 configurations. It doesn’t seem likely this feature would be provided without also allowing cache lines to be shared across the clusters. Could anyone point me in the right direction? Thanks, Arteen _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
