Ok, So first step is to create a wrapper that all timers fire through, then an array to count the number of invocations per timer_id, after that some per timer_id time accounting.
Will let you know if its anything outside my application. On Mon, 13 Jan 2020 at 15:01, Joel Sherrill <j...@rtems.org> wrote: > > > On Mon, Jan 13, 2020 at 8:53 AM Matthew J Fletcher <ami...@gmail.com> > wrote: > >> Hi, >> >> My application seems to be using around 1/3rd of its total cpu usage in >> the 'TIME' task,. is this the task created by rtems_timer_initiate_server() >> ? >> > > Yes. > >> >> What would be the best way to get more information,. are there console >> commands that would emit more data, or do i need to instrument my >> application to see usage of all rtems_timer_xx callbacks ? >> > > rtems_timer_server_xx would be the ones going to the TIME Server. > > But 1/3 seems quite excessive. I would assume one of your timer server > routines is doing something unexpectedly heavy CPU-wise. > > I don't think there is any instrumentation in the server which would help. > Measuring the execution time of each invocation is what comes to mind. My > first thought is that this would be a nice debug option for timers. But I > am not sure how good this would be for ISR style. > > --joel > >> >> regards >> --- >> Matthew J Fletcher >> >> _______________________________________________ >> users mailing list >> users@rtems.org >> http://lists.rtems.org/mailman/listinfo/users > > -- regards --- Matthew J Fletcher
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
