public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: 2.6.17-rt1
Date: Wed, 21 Jun 2006 20:57:27 -0400	[thread overview]
Message-ID: <1150937848.2754.379.camel@mindpipe> (raw)
In-Reply-To: <20060618070641.GA6759@elte.hu>

On Sun, 2006-06-18 at 09:06 +0200, Ingo Molnar wrote:
> i have released the 2.6.17-rt1 tree, which can be downloaded from the 
> usual place:
> 
>    http://redhat.com/~mingo/realtime-preempt/
> 
> this is a fixes-only release: merged to 2.6.17-final and smaller fixes.
> 
> to build a 2.6.17-rc6-rt1 tree, the following patches should be applied:
> 
>   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.17.tar.bz2
>   http://redhat.com/~mingo/realtime-preempt/patch-2.6.17-rt1

I'm getting some strange latency tracer output on a dual core AMD box.
Why does it start at 404us?

Lee

preemption latency trace v1.1.5 on 2.6.17-rt1-smp-latency-trace
--------------------------------------------------------------------
 latency: 415 us, #26/26, CPU#1 | (M:rt VP:0, KP:0, SP:1 HP:1 #P:2)
    -----------------
    | task: kjournald-2043 (uid:0 nice:-5 policy:0 rt_prio:0)
    -----------------

                 _------=> CPU#            
                / _-----=> irqs-off        
               | / _----=> need-resched    
               || / _---=> hardirq/softirq 
               ||| / _--=> preempt-depth   
               |||| /                      
               |||||     delay             
   cmd     pid ||||| time  |   caller      
      \   /    |||||   \   |   /           
  <idle>-0     1Dn.1  404us : smp_reschedule_interrupt (reschedule_interrupt)
  <idle>-0     1.n.1  405us : __exit_idle (cpu_idle)
  <idle>-0     1.n.1  405us : atomic_notifier_call_chain (__exit_idle)
  <idle>-0     1.n.1  406us : rcu_read_lock (atomic_notifier_call_chain)
  <idle>-0     1Dn.1  406us : rcu_read_lock (0 0 badc)
  <idle>-0     1Dn.1  406us : rcu_read_lock (ffff810002eb7228 0 badc)
  <idle>-0     1.n.1  406us : rcu_read_unlock (atomic_notifier_call_chain)
  <idle>-0     1Dn.1  407us : rcu_read_unlock (ffff810002eb7228 0 1)
  <idle>-0     1Dn.1  407us : rcu_read_unlock (0 0 0)
  <idle>-0     1Dn..  407us : __schedule (cpu_idle)
  <idle>-0     1Dn..  407us : profile_hit (__schedule)
  <idle>-0     1Dn.1  408us : sched_clock (__schedule)
  <idle>-0     1Dn.1  408us : _raw_spin_lock_irq (__schedule)
  <idle>-0     1Dn.2  409us : recalc_task_prio (__schedule)
  <idle>-0     1Dn.2  410us : effective_prio (recalc_task_prio)
  <idle>-0     1Dn.2  410us : effective_prio <<...>-2043> (-10 -10)
  <idle>-0     1D..2  412us : __switch_to (thread_return)
   <...>-2043  1D..2  413us : thread_return <<idle>-0> (20 -10)
   <...>-2043  1D..2  413us : _raw_spin_unlock_irq (thread_return)
   <...>-2043  1...1  413us : constant_test_bit (_raw_spin_unlock_irq)
   <...>-2043  1...1  413us : trace_stop_sched_switched (thread_return)
   <...>-2043  1D..1  414us : _raw_spin_lock (trace_stop_sched_switched)
   <...>-2043  1D..2  414us : trace_stop_sched_switched <<...>-2043> (110 1)
   <...>-2043  1D..2  415us : thread_return (thread_return)




  parent reply	other threads:[~2006-06-22  0:57 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18  7:06 2.6.17-rt1 Ingo Molnar
2006-06-18 16:13 ` 2.6.17-rt1 Michal Piotrowski
     [not found] ` <Pine.LNX.4.64.0606201656230.11643@localhost.localdomain>
2006-06-20 15:13   ` Why can't I set the priority of softirq-hrt? (Re: 2.6.17-rt1) Thomas Gleixner
2006-06-20 17:09     ` Esben Nielsen
2006-06-20 16:35       ` Thomas Gleixner
2006-06-20 21:16         ` Esben Nielsen
2006-06-20 20:35           ` Thomas Gleixner
2006-06-20 23:19             ` Esben Nielsen
2006-06-20 16:39       ` Steven Rostedt
2006-06-20 18:12         ` Esben Nielsen
2006-06-20 17:21           ` Thomas Gleixner
2006-06-20 21:26             ` Esben Nielsen
2006-06-20 20:51               ` Thomas Gleixner
2006-06-21  8:20               ` Steven Rostedt
2006-06-21 11:05                 ` Esben Nielsen
2006-06-21 15:43                   ` Esben Nielsen
2006-06-21 15:21                     ` Steven Rostedt
2006-06-21 16:37                       ` Esben Nielsen
2006-06-21 15:51                         ` Steven Rostedt
2006-06-21 17:14                           ` Esben Nielsen
2006-06-21 16:26                     ` Thomas Gleixner
2006-06-21 18:30                       ` Ingo Molnar
2006-06-22 10:28                         ` Esben Nielsen
2006-06-21 21:29                       ` Esben Nielsen
2006-06-21 20:33                         ` Thomas Gleixner
2006-06-21 23:35                           ` Esben Nielsen
2006-06-22  7:06                             ` Thomas Gleixner
2006-06-22 10:32                               ` Esben Nielsen
2006-06-22 13:33                               ` Steven Rostedt
2006-06-22 13:45                       ` Steven Rostedt
2006-06-22 14:20                         ` Thomas Gleixner
2006-06-22 14:23                           ` Steven Rostedt
2006-06-22 14:26                             ` Thomas Gleixner
2006-06-22 18:06                               ` Esben Nielsen
2006-06-22 18:05                                 ` Thomas Gleixner
2006-06-23 11:23                                   ` Esben Nielsen
2006-06-23 11:06                                     ` Steven Rostedt
2006-07-03 11:48                                     ` Esben Nielsen
2006-06-21  8:13           ` Steven Rostedt
2006-06-21 11:03             ` Esben Nielsen
2006-06-22  0:57 ` Lee Revell [this message]
2006-06-22  2:51   ` More weird latency trace output (was 2.6.17-rt1) Lee Revell
2006-06-23  1:24     ` Lee Revell
2006-06-24 22:15       ` Lee Revell
2006-06-24 22:12         ` Ingo Molnar
2006-06-24 22:31           ` Lee Revell
2006-06-24 23:49           ` Lee Revell
2006-06-23 20:56 ` 2.6.17-rt1 - mm_struct leak Vernon Mauery
2006-06-24  9:24   ` Mark Hounschell
2006-06-24  9:32     ` Mark Hounschell
2006-06-30 16:02   ` [PATCH -RT]Re: " Vernon Mauery

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=1150937848.2754.379.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox