From: John Sigler <linux.kernel@free.fr>
To: Alessio Igor Bogani <abogani@texware.it>
Cc: linux-rt-users@vger.kernel.org, linux-acpi@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: High resolution timers on ACPI-less kernel
Date: Tue, 09 Oct 2007 11:28:29 +0200 [thread overview]
Message-ID: <470B49BD.4070506@free.fr> (raw)
In-Reply-To: <1191921343.13628.0.camel@godzilla.tecnorama.it>
Alessio Igor Bogani wrote:
> On Tue, 2007-10-09 at 11:06 +0200, John Sigler wrote:
> [...]
>> I enabled high resolution timer support and disabled ACPI support.
> [...]
>
> http://www.mail-archive.com/linux-rt-users@vger.kernel.org/msg00375.html
There are other clock sources on my system.
The timestamp counter is reliable (as far as I can tell).
The LAPIC timer is reliable.
(I've just disabled the PM timer.)
# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
tsc pit jiffies
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
# cat /proc/timer_list
Timer List Version: v0.3
HRTIMER_MAX_CLOCK_BASES: 2
now at 3787164271418 nsecs
cpu: 0
clock 0:
.index: 0
.resolution: 10000000 nsecs
.get_time: ktime_get_real
.offset: 0 nsecs
active timers:
clock 1:
.index: 1
.resolution: 10000000 nsecs
.get_time: ktime_get
.offset: 0 nsecs
active timers:
#0: <cf22bec0>, it_real_fn, S:01
# expires at 3789432883979 nsecs [in 2268612561 nsecs]
.expires_next : 9223372036854775807 nsecs
.hres_active : 0
.nr_events : 0
.nohz_mode : 0
.idle_tick : 0 nsecs
.tick_stopped : 0
.idle_jiffies : 0
.idle_calls : 0
.idle_sleeps : 0
.idle_entrytime : 0 nsecs
.idle_sleeptime : 0 nsecs
.last_jiffies : 0
.next_jiffies : 0
.idle_expires : 0 nsecs
jiffies: 348693
Tick Device: mode: 0
Clock Event Device: pit
max_delta_ns: 27461866
min_delta_ns: 12571
mult: 5124677
shift: 32
mode: 1
next_event: 0 nsecs
set_next_event: pit_next_event
set_mode: init_pit_timer
event_handler: clockevents_handle_noop
tick_broadcast_mask: 00000000
tick_broadcast_oneshot_mask: 00000000
Tick Device: mode: 0
Clock Event Device: lapic
max_delta_ns: 1006581321
min_delta_ns: 1799
mult: 35793226
shift: 32
mode: 2
next_event: 0 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: tick_handle_periodic
Regards.
next prev parent reply other threads:[~2007-10-09 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 9:06 High resolution timers on ACPI-less kernel John Sigler
2007-10-09 9:15 ` Alessio Igor Bogani
2007-10-09 9:28 ` John Sigler [this message]
2007-10-09 9:34 ` Thomas Gleixner
2007-10-09 10:35 ` John Sigler
2007-10-09 15:59 ` Dragan Noveski
2007-10-09 17:13 ` Thomas Gleixner
2007-10-11 10:37 ` Dragan Noveski
2007-10-09 9:20 ` John Sigler
2007-10-09 9:22 ` Thomas Gleixner
2007-10-09 9:39 ` John Sigler
2007-10-09 9:48 ` Alessio Igor Bogani
2007-10-09 9:53 ` Thomas Gleixner
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=470B49BD.4070506@free.fr \
--to=linux.kernel@free.fr \
--cc=abogani@texware.it \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.