Hi Balazs,
What you suggest sounds like a panacea! I'm not sure it's possible, though
:(.
There are multiple different levels of fidelity between the O3 CPU and the
Timing Simple CPU. You could imagine other CPU models with more or less
fidelity as well, but currently these are the two main
Hello,
Yeah, adding flush to a protocol is a pretty large task, but it shouldn't
be too difficult. The key difficulty will be testing it, but the Ruby
tester does support testing flushes (probably not out of the box with
ruby_random_test.py, though).
There's no particular reason except that we
Hi Daecheol,
Unfortunately, the flush command is a bit more complicated to implement
than just a simple replacement. I responded to another message about this
on the mailing list a few minutes ago that you can see for more information.
Cheers,
Jason
On Mon, Sep 28, 2020 at 8:59 PM Daecheol You
Hi Kavya,
This looks like a bug! The RubyPrefetcher has never been regularly tested,
as far as I know. I would guess the place where these were updated got
deleted at some point and no one noticed. I'd try checking out a gem5 from
5 years ago and see if it's there. We would welcome a contribution
Hi Shougang,
I think you can use .value() to get the actual value out of the stat.
That should be easy to cast to an unsigned, if needed.
However, I think there might be some confusion on how to register/use the
stats. If you've registered it correctly and it is updated during
simulation (e.g.,
Hi everyone,
We are sending this email to be as transparent as possible. The gem5
community is respectful and inclusive of all people, and we enforce these
standards in all community spaces. We as members, contributors, and leaders
pledge to make participation in our community a harassment-free
