Research gettimeofday() optimizattions for ARM platforms

Registered by Deepak Saxena on 2011-06-03

Research whether optimizations can be made to ARM's gettimeofday() code path to decrease context switches and accelerate performance.

Blueprint information

Status:
Started
Approver:
None
Priority:
Low
Drafter:
Deepak Saxena
Direction:
Needs approval
Assignee:
Jason Liu
Definition:
Approved
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Jason Liu on 2011-09-14

Related branches

Sprints

Whiteboard

Investigate whether mapping the SOC timer registers into userspace can work across different SOC families
(OMAP, i.mx, Samsung, Davinci, etc):

Investigate if timer rate will change as CPU freq is changed on different SOC families,

+3[r64343]:Issues of how to handle the wrap issues and how to get the correct time(since 1970): No Solution Now.

investigate mapping the SOC timer registers into userspace on i.MX reults
 i.MX timer register can be seen from userspace by mapping it to user space address.

investigate mapping the SOC timer registers into userspace on i.MX results
   It depends on SOC platforms, for i.MX5 the GPT timer will not change during dvfs.

(?)

Work Items

Work items:
investigate mapping the SOC timer registers into userspace on i.MX: DONE
investigate mapping the SOC timer registers into userspace on OMAP: INPROGRESS
investigate mapping the SOC timer registers into userspace on Samsung: TODO
Investigate mapping the SOC timer registers into userspace on Davinci: TODO
investigate mapping the SOC timer registers into userspace on i.MX: DONE
investigate mapping the SOC timer registers into userspace on OMAP: INPROGRESS
investigate mapping the SOC timer registers into userspace on Samsung: TODO
investigate mapping the SOC timer registers into userspace on Davinci: TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.