Great, now I see the reason that they check for non-caching cpu in scripts.
We used to use AtomicSimpleCPU and fastmem option for checkpointing, and
NonCachingSimpleCPU is a replacement for this.
Thanks Daniel and Abhishek,
Ali
On Sun, Mar 15, 2020 at 8:23 AM Daniel Carvalho wrote:
> In
In particular, the following description seems to be relevant to your
questions:
"Simple CPU model based on the atomic CPU. Unlike the atomic CPU, this model
causes the memory system to bypass caches and is therefore slightly faster in
some cases. However, its main purpose is as a substitute
Hi,
I do not know the reason for that. But if you want to create simpoints
which will be used by O3CPU, you should use the AtomicSimpleCPU with
"--caches" option and also add "--l2cache" if your O3CPU is using L2 cache.
Best regards,
Abhishek
On Sat, Mar 14, 2020 at 5:53 PM Ali Hajiabadi
Thanks for your reply. But se.py script checks that the CPU type is
non-caching. Is there a reason for that? Can I ignore those checks?
On Sun, Mar 15, 2020 at 5:41 AM Abhishek Singh <
abhishek.singh199...@gmail.com> wrote:
> Hi,
> I would advise using Atomic Simple Cpu with “—caches” option to
Hi,
I would advise using Atomic Simple Cpu with “—caches” option to create
Simpoints
On Sat, Mar 14, 2020 at 5:35 PM Ali Hajiabadi
wrote:
> Hi everyone,
>
> What is the difference between using NonCachingSimpleCPU
> and AtomicSimpleCPU in order to profile and taking simpoints and
>
Hi everyone,
What is the difference between using NonCachingSimpleCPU
and AtomicSimpleCPU in order to profile and taking simpoints and
checkpoints? I want to use checkpoints to simulate and evaluate my own
modified version of O3 core model. Which CPU type is the best to profile
and take
