Arm Community
Site
Search
User
Site
Search
User
Support forums
Arm Development Studio forum
RVDS3.1 page table option for profiling
Jump...
Cancel
Locked
Locked
Replies
4 replies
Subscribers
118 subscribers
Views
3047 views
Users
0 members are here
Options
Share
More actions
Cancel
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
RVDS3.1 page table option for profiling
RaghavendraPrasad RaghavendraPrasad
over 12 years ago
Note: This was originally posted on 29th July 2009 at
http://forums.arm.com
Hi all,
I'm using Realview3.1 Debugger connected to ARM1176JZFS core. I want to know the total no of cycles for my code. when I 'm connectiong the debugger with "Default page table" option enabled, the cycles that I got from cycle count register is less than the cycle count that I got without enabling the "Default page table" option. I don't know whether to enable thr option for calculating the total cycles. Can any one help in this regard. Thanks in advance.
Thanks & Regards,
M. Raghavendra
Parents
Martin Weidmann
over 12 years ago
Note: This was originally posted on 30th July 2009 at
http://forums.arm.com
The default page table option starts the simulator with the MMU (or MPU) pre-enabled. It saves you writing your own MMU/MPU initialization code, which is useful for quick tests. It is the MMU/MPU which controls what is cacheable, so having these pre-enabled can have a big impact on performance.
Cancel
Vote up
0
Vote down
Cancel
Reply
Martin Weidmann
over 12 years ago
Note: This was originally posted on 30th July 2009 at
http://forums.arm.com
The default page table option starts the simulator with the MMU (or MPU) pre-enabled. It saves you writing your own MMU/MPU initialization code, which is useful for quick tests. It is the MMU/MPU which controls what is cacheable, so having these pre-enabled can have a big impact on performance.
Cancel
Vote up
0
Vote down
Cancel
Children
No data