From: Stanislav Meduna <stano@meduna.org>
To: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Highres timers broken on i.mx28 for CONFIG_HZ_PERIODIC
Date: Tue, 11 Nov 2014 01:55:37 +0100 [thread overview]
Message-ID: <54615E89.7020902@meduna.org> (raw)
Hi,
something between 3.12.19(-rt30) and 3.12.31(-rt45) broke
hrtimers on (at least) i.MX28 for CONFIG_HZ_PERIODIC.
Switching to CONFIG_NO_HZ_IDLE restores them.
Is this the expected behaviour or a regression?
The difference in the /proc/timer_list is the
Tick Device: mode: 0 (new) or 1 (old)
# cat /proc/timer_list
Timer List Version: v0.7
HRTIMER_MAX_CLOCK_BASES: 4
now at 3551448891259 nsecs
cpu: 0
clock 0:
.base: c03694e0
.index: 0
.resolution: 4000000 nsecs
.get_time: ktime_get
.offset: 0 nsecs
active timers:
...
clock 1:
.base: c0369520
.index: 1
.resolution: 4000000 nsecs
.get_time: ktime_get_real
.offset: 0 nsecs
active timers:
clock 2:
.base: c0369560
.index: 2
.resolution: 4000000 nsecs
.get_time: ktime_get_boottime
.offset: 0 nsecs
active timers:
clock 3:
.base: c03695a0
.index: 3
.resolution: 4000000 nsecs
.get_time: ktime_get_clocktai
.offset: 0 nsecs
active timers:
.expires_next : 9223372036854775807 nsecs
.hres_active : 0
.nr_events : 0
.nr_retries : 0
.nr_hangs : 0
.max_hang_time : 0 nsecs
.nohz_mode : 0
.last_tick : 0 nsecs
.tick_stopped : 0
.idle_jiffies : 0
.idle_calls : 0
.idle_sleeps : 0
.idle_entrytime : 0 nsecs
.idle_waketime : 0 nsecs
.idle_exittime : 0 nsecs
.idle_sleeptime : 0 nsecs
.iowait_sleeptime: 0 nsecs
.last_jiffies : 0
.next_jiffies : 0
.idle_expires : 0 nsecs
jiffies: 812862
Tick Device: mode: 0
Per CPU device: 0
Clock Event Device: mxs_timrot
max_delta_ns: 178956969028
min_delta_ns: 1000
mult: 51539608
shift: 31
mode: 3
next_event: 3551452000000 nsecs
set_next_event: timrotv2_set_next_event
set_mode: mxs_set_mode
event_handler: tick_handle_periodic
retries: 0
In the 3.2.19 it was
Timer List Version: v0.7
HRTIMER_MAX_CLOCK_BASES: 4
now at 280235727915168 nsecs
cpu: 0
clock 0:
.base: c03654c0
.index: 0
.resolution: 1 nsecs
.get_time: ktime_get
.offset: 0 nsecs
active timers:
...
clock 1:
.base: c0365500
.index: 1
.resolution: 1 nsecs
.get_time: ktime_get_real
.offset: 1415385038639056250 nsecs
active timers:
clock 2:
.base: c0365540
.index: 2
.resolution: 1 nsecs
.get_time: ktime_get_boottime
.offset: 0 nsecs
active timers:
clock 3:
.base: c0365580
.index: 3
.resolution: 1 nsecs
.get_time: ktime_get_clocktai
.offset: 1415385038639056250 nsecs
active timers:
.expires_next : 280235730396263 nsecs
.hres_active : 1
.nr_events : 207916570
.nr_retries : 2164032
.nr_hangs : 7
.max_hang_time : 107499 nsecs
.nohz_mode : 0
.last_tick : 0 nsecs
.tick_stopped : 0
.idle_jiffies : 0
.idle_calls : 0
.idle_sleeps : 0
.idle_entrytime : 0 nsecs
.idle_waketime : 0 nsecs
.idle_exittime : 0 nsecs
.idle_sleeptime : 0 nsecs
.iowait_sleeptime: 0 nsecs
.last_jiffies : 0
.next_jiffies : 0
.idle_expires : 0 nsecs
jiffies: 69983932
Tick Device: mode: 1
Per CPU device: 0
Clock Event Device: mxs_timrot
max_delta_ns: 178956969028
min_delta_ns: 1000
mult: 51539608
shift: 31
mode: 3
next_event: 280235730396263 nsecs
set_next_event: timrotv2_set_next_event
set_mode: mxs_set_mode
event_handler: hrtimer_interrupt
retries: 0
Thanks
--
Stano
next reply other threads:[~2014-11-11 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 0:55 Stanislav Meduna [this message]
2015-02-17 14:01 ` Highres timers broken on i.mx28 for CONFIG_HZ_PERIODIC Sebastian Andrzej Siewior
2015-03-05 17:54 ` Stanislav Meduna
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54615E89.7020902@meduna.org \
--to=stano@meduna.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.