From: Chris Wright <chrisw@sous-sol.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
LKML <linux-kernel@vger.kernel.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
john stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] x86-64 highres/dyntick support
Date: Tue, 8 May 2007 03:06:57 -0700 [thread overview]
Message-ID: <20070508100657.GZ3505@sequoia.sous-sol.org> (raw)
In-Reply-To: <1178618304.3042.320.camel@localhost.localdomain>
* Thomas Gleixner (tglx@linutronix.de) wrote:
> Hmm, that's even more strange. Can you please provide the output
> of /proc/timer_list ?
It's quite normal looking, and a printk in clockevents_set_mode looks normal too.
[chrisw@localhost ~]$ cat /proc/timer_list
Timer List Version: v0.3
HRTIMER_MAX_CLOCK_BASES: 2
now at 313565930359 nsecs
cpu: 0
clock 0:
.index: 0
.resolution: 4000250 nsecs
.get_time: ktime_get_real
active timers:
clock 1:
.index: 1
.resolution: 4000250 nsecs
.get_time: ktime_get
active timers:
#0: <ffff810150223e38>, hrtimer_wakeup, S:01
# expires at 313700587872 nsecs [in 134657513 nsecs]
#1: <ffff810150223e38>, it_real_fn, S:01
# expires at 332024684987 nsecs [in 18458754628 nsecs]
#2: <ffff810150223e38>, hrtimer_wakeup, S:01
# expires at 337032779067 nsecs [in 23466848708 nsecs]
#3: <ffff810150223e38>, hrtimer_wakeup, S:01
# expires at 1851212334864 nsecs [in 1537646404505 nsecs]
#4: <ffff810150223e38>, it_real_fn, S:01
# expires at 3635317355388 nsecs [in 3321751425029 nsecs]
#5: <ffff810150223e38>, it_real_fn, S:01
# expires at 3635630194993 nsecs [in 3322064264634 nsecs]
cpu: 1
clock 0:
.index: 0
.resolution: 4000250 nsecs
.get_time: ktime_get_real
active timers:
clock 1:
.index: 1
.resolution: 4000250 nsecs
.get_time: ktime_get
active timers:
cpu: 2
clock 0:
.index: 0
.resolution: 4000250 nsecs
.get_time: ktime_get_real
active timers:
clock 1:
.index: 1
.resolution: 4000250 nsecs
.get_time: ktime_get
active timers:
cpu: 3
clock 0:
.index: 0
.resolution: 4000250 nsecs
.get_time: ktime_get_real
active timers:
clock 1:
.index: 1
.resolution: 4000250 nsecs
.get_time: ktime_get
active timers:
#0: <ffff810150223e38>, it_real_fn, S:01
# expires at 313558625026 nsecs [in -7305333 nsecs]
#1: <ffff810150223e38>, hrtimer_wakeup, S:01
# expires at 369334850252 nsecs [in 55768919893 nsecs]
#2: <ffff810150223e38>, it_real_fn, S:01
# expires at 3936979059363 nsecs [in 3623413129004 nsecs]
Tick Device: mode: 0
Clock Event Device: hpet
max_delta_ns: 85899346200
min_delta_ns: 1920
mult: 107374182
shift: 32
mode: 2
next_event: 9223372036854775807 nsecs
set_next_event: hpet_next_event
set_mode: hpet_set_mode
event_handler: tick_handle_periodic_broadcast
tick_broadcast_mask: 00000001
Tick Device: mode: 0
Clock Event Device: lapic
max_delta_ns: 671088687
min_delta_ns: 1200
mult: 53687081
shift: 32
mode: 1
next_event: 0 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: tick_handle_periodic
Tick Device: mode: 0
Clock Event Device: lapic
max_delta_ns: 671088687
min_delta_ns: 1200
mult: 53687081
shift: 32
mode: 2
next_event: 0 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: tick_handle_periodic
Tick Device: mode: 0
Clock Event Device: lapic
max_delta_ns: 671088687
min_delta_ns: 1200
mult: 53687081
shift: 32
mode: 2
next_event: 0 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: tick_handle_periodic
Tick Device: mode: 0
Clock Event Device: lapic
max_delta_ns: 671088687
min_delta_ns: 1200
mult: 53687081
shift: 32
mode: 2
next_event: 0 nsecs
set_next_event: lapic_next_event
set_mode: lapic_timer_setup
event_handler: tick_handle_periodic
[chrisw@localhost ~]$ grep -e 0: -e LOC: /proc/interrupts
0: 72 2 58 36008 IO-APIC-edge timer
LOC: 36655 36772 36725 36683
[chrisw@localhost ~]$ grep -e 0: -e LOC: /proc/interrupts
0: 72 2 58 36165 IO-APIC-edge timer
LOC: 36812 36929 36882 36840
[chrisw@localhost ~]$ grep -e 0: -e LOC: /proc/interrupts
0: 72 2 58 36297 IO-APIC-edge timer
LOC: 36944 37061 37014 36972
[chrisw@localhost ~]$ grep -e 0: -e LOC: /proc/interrupts
0: 72 2 58 36424 IO-APIC-edge timer
LOC: 37071 37188 37141 37099
next prev parent reply other threads:[~2007-05-08 10:07 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 20:58 Thomas Gleixner
2007-05-07 9:16 ` Nicolas Mailhot
2007-05-07 15:28 ` Thomas Gleixner
2007-05-08 17:08 ` Nicolas Mailhot
2007-05-07 16:31 ` Chris Wright
2007-05-07 16:46 ` Thomas Gleixner
2007-05-07 17:18 ` Chris Wright
2007-05-08 9:39 ` Chris Wright
2007-05-08 9:42 ` [PATCH 1/5] x86_64: tsc compile fix Chris Wright
2007-05-08 9:47 ` Thomas Gleixner
2007-05-08 9:43 ` [PATCH 2/5] x86_64: __setup_APIC_LVTT whitespace fix Chris Wright
2007-05-08 9:48 ` Thomas Gleixner
2007-05-08 9:44 ` [PATCH 3/5] i386: hpet assumes boot cpu is 0 Chris Wright
2007-05-08 9:54 ` Thomas Gleixner
2007-05-08 9:46 ` [PATCH 4/5] i386: i8253 clockevent shutdown and unused using pit Chris Wright
2007-05-08 9:53 ` Thomas Gleixner
2007-05-08 9:47 ` [PATCH 5/5] x86_64: restore restore nohpet cmdline Chris Wright
2007-05-08 9:53 ` Thomas Gleixner
2007-05-08 9:51 ` [PATCH] x86-64 highres/dyntick support Thomas Gleixner
2007-05-08 9:51 ` Chris Wright
2007-05-08 9:58 ` Thomas Gleixner
2007-05-08 10:06 ` Chris Wright [this message]
2007-05-08 10:34 ` Thomas Gleixner
2007-05-08 13:15 ` Pallipadi, Venkatesh
2007-05-07 22:43 ` Venki Pallipadi
2007-05-07 23:15 ` Thomas Gleixner
2007-05-14 1:17 ` Alistair John Strachan
2007-05-14 6:33 ` Thomas Gleixner
2007-05-14 10:26 ` [PATCH] x86-64 highres/dyntick support 2.6.22-rc1-v1 Thomas Gleixner
2007-05-14 20:10 ` Valdis.Kletnieks
2007-05-14 20:23 ` Thomas Gleixner
2007-05-14 21:15 ` Alistair John Strachan
2007-05-14 22:05 ` Thomas Gleixner
2007-05-14 22:42 ` Alistair John Strachan
2007-05-15 8:18 ` [PATCH] x86-64 highres/dyntick support 2.6.22-rc1-v4 Thomas Gleixner
2007-05-15 14:06 ` Frank Sorenson
2007-05-15 21:53 ` Thomas Gleixner
2007-05-15 23:20 ` Frank Sorenson
2007-05-16 5:02 ` Frank Sorenson
2007-05-16 6:20 ` Thomas Gleixner
2007-05-16 9:01 ` Thomas Gleixner
2007-05-15 23:23 ` Alistair John Strachan
2007-05-16 5:54 ` Thomas Gleixner
2007-05-16 10:03 ` [PATCH] x86-64 highres/dyntick support 2.6.22-rc1-v5 Thomas Gleixner
2007-05-16 19:48 ` Frank Sorenson
2007-05-17 4:25 ` Frank Sorenson
2007-05-17 19:12 ` Frank Sorenson
2007-05-17 19:19 ` Christoph Lameter
2007-05-18 3:55 ` Frank Sorenson
2007-05-18 16:58 ` Christoph Lameter
2007-05-18 19:44 ` Christoph Lameter
2007-05-17 22:09 ` [PATCH] x86-64 highres/dyntick support 2.6.22-rc1-v7 Thomas Gleixner
2007-05-21 1:14 ` Valdis.Kletnieks
2007-05-07 12:07 [PATCH] x86-64 highres/dyntick support Mats Johannesson
2007-05-07 15:13 ` 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=20070508100657.GZ3505@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome