Architected timer not being used by default on Arndale
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Arndale |
Fix Released
|
Undecided
|
Unassigned | ||
Linaro Linux Baseline |
Fix Released
|
Undecided
|
Andrey Konovalov | ||
linaro-landing-team-samsung |
Fix Released
|
Medium
|
Tushar Behera |
Bug Description
Hi,
The Exynos 5250 includes an architected timer which is on core and very cheap to read.
This appears on dmesg on bootup, but is not in use by default:
# cat /sys/devices/
mct-frc
We can manually enable the architected timer via:
# echo "arch_sys_counter" > /sys/devices/
Switching to clocksource arch_sys_counter
Enabling the architected timer can lead to a significant performance improvement for timer sensitive workloads such as TCP/IP.
It turns out that both arch_sys_counter and mct-frc have a rating of 400.
On bootup, arch_sys_counter is initialised first then the clocksource changes to mct-frc when that initialises later on.
If the rating of mct-frc is reduced below 400 (in arch/arm/
Best,
--
Steve
(This applies to the latest linaro tracking tree).
Changed in linaro-linux-baseline: | |
milestone: | none → 13.04 |
assignee: | nobody → Andrey Konovalov (andrey-konovalov) |
Changed in linaro-landing-team-samsung: | |
assignee: | nobody → Tushar Behera (tusharbehera) |
milestone: | none → 2013.04 |
importance: | Undecided → Medium |
Changed in linaro-landing-team-samsung: | |
status: | In Progress → Fix Committed |
Changed in linaro-linux-baseline: | |
status: | New → Fix Released |
Changed in linaro-landing-team-samsung: | |
status: | Fix Committed → Fix Released |
Changed in arndale: | |
status: | New → Fix Released |
If there is a way to measure the performance difference with arch_sys_counter is available, that would be better.
The changes regarding mct-frc would be committed with 3.9-rc7 release.