Yes, I did :).

--
Dr. Bobby R. Bruce
Room 2235,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: https://www.bobbybruce.net


On Thu, Oct 15, 2020 at 1:48 PM Gabe Black <gabebl...@google.com> wrote:

> I think you mean the TimingSimpleCPU, not the AtomicTimingCPU.
>
> Gabe
>
> On Thu, Oct 15, 2020 at 1:41 PM Bobby Bruce via gem5-users <
> gem5-users@gem5.org> wrote:
>
>> Hey Krishnan,
>>
>> Linux does take about 45 minutes or so to run using AtomicSimpleCPU.
>> You're not doing anything wrong in this regard. I'm afraid there's no
>> information I can give you on making it faster. Anything to make this
>> significantly faster, would be sacrificing the accuracy of simulation. This
>> a problem, across the board, for architecture simulators.
>>
>> KVMCPU is certainly faster but, given what else you've been saying, you
>> wish to do real simulations and gather statistics. The KVMCPU is not the
>> right tool for this. It doesn't simulate anything. It doesn't have timing
>> information. AtomicSimpleCPU is also not suitable. I'd recommend using the
>> AtomicTimingCPU, which will give you a decent simulation and stats output.
>>
>> Kind regards,
>> Bobby
>> --
>> Dr. Bobby R. Bruce
>> Room 2235,
>> Kemper Hall, UC Davis
>> Davis,
>> CA, 95616
>>
>> web: https://www.bobbybruce.net
>>
>>
>> On Thu, Oct 15, 2020 at 1:50 AM krishnan gosakan via gem5-users <
>> gem5-users@gem5.org> wrote:
>>
>>> Hi all.
>>> I hope everyone is doing good. I recently started working with gem5
>>> simulator. I am trying to do some modification to the page table walker
>>> (pagetable_walker). My problem is that booting linux under full system
>>> emulation is very slow. It takes nearly 30 to 40 minutes to boot. I am
>>> using AtomicSimpleCPU. I just want to know if this is the normal case for
>>> this cpu type.
>>>
>>> I also tried with X86KvmCPU and I used the following command,
>>> $gem5_dir/build/X86/gem5.opt $gem5_config_dir/example/fs.py --kernel
>>> $linux_dir/vmlinux --disk-image $cur_dir/qemu-image.img --caches --l2cache
>>> --cpu-type X86KvmCPU --fast-forward 1000000000
>>>
>>> This was faster than atomic simple cpu but the problem here is that all
>>> stats are cleared up at the end. I shall attach an example stat file with
>>> this email. In the stat file attached, you may see all the tlb stats
>>> cleared. I wish to know the reason why stats are cleared in examples/fs.py
>>>
>>> I just want to know if there is any way to fasten boot up with an atomic
>>> simple cpu or is this normal? My work is basically to change the kernel,
>>> compile it, run under gem5 and check the stats.
>>> Any kind of suggestions are most appreciated.
>>> Thank you.
>>> --
>>> Regards,
>>> Krishnan.
>>> _______________________________________________
>>> gem5-users mailing list -- gem5-users@gem5.org
>>> To unsubscribe send an email to gem5-users-le...@gem5.org
>>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>>
>> _______________________________________________
>> gem5-users mailing list -- gem5-users@gem5.org
>> To unsubscribe send an email to gem5-users-le...@gem5.org
>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
>
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to