Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269713AbUICRji (ORCPT ); Fri, 3 Sep 2004 13:39:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269611AbUICRi6 (ORCPT ); Fri, 3 Sep 2004 13:38:58 -0400 Received: from pD95171CA.dip.t-dialin.net ([217.81.113.202]:49793 "EHLO undata.org") by vger.kernel.org with ESMTP id S269705AbUICRgm (ORCPT ); Fri, 3 Sep 2004 13:36:42 -0400 Subject: Re: [patch] voluntary-preempt-2.6.9-rc1-bk4-R1 From: Thomas Charbonnel To: Ingo Molnar Cc: Lee Revell , Free Ekanayaka , Eric St-Laurent , linux-kernel , "K.R. Foley" , Felipe Alfaro Solana , Daniel Schmitt , Mark_H_Johnson@raytheon.com, "P.O. Gaillard" , nando@ccrma.stanford.edu, luke@audioslack.com, free78@tin.it In-Reply-To: <1094228060.5492.8.camel@localhost> References: <1094181447.4815.6.camel@orbiter> <1094192788.19760.47.camel@krustophenia.net> <20040903063658.GA11801@elte.hu> <1094194157.19760.71.camel@krustophenia.net> <20040903070500.GB13100@elte.hu> <1094197233.19760.115.camel@krustophenia.net> <87acw7bxkh.fsf@agnula.org> <1094198755.19760.133.camel@krustophenia.net> <20040903092547.GA18594@elte.hu> <1094211218.5453.3.camel@localhost> <20040903114949.GA29493@elte.hu> <1094228060.5492.8.camel@localhost> Content-Type: text/plain Message-Id: <1094232995.5492.11.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 03 Sep 2004 19:36:35 +0200 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3973 Lines: 81 I wrote : > Ingo Molnar wrote : > > this is a pretty weird one. First it shows an apparently non-monotonic > > RDTSC: the jump forward and backward in time around profile_hit. I > > suspect the real RDTSC value was lower than the previous one and caused > > an underflow. What is your cpu_khz in /proc/cpuinfo? > > > > the other weird one is the +0.595 usec entry at notifier_call_chain(). > > That code is just a couple of instructions, so no real for any overhead > > there. > > > > could you try the attached robust-get-cycles.patch ontop of your current > > tree and see whether it impacts these weirdnesses? The patch makes sure > > that the cycle counter is sane: two subsequent readings of it were > > monotonic and less than 1000 cycles apart. > > > > this patch probably wont remove the +0.595 msec latency though - the > > RDTSC value jumped forward there permanently. Maybe the RDTSC value is > > somehow corrupted by NMIs - could you turn off the NMI watchdog to > > check? > > Here are more traces with robust-get-cycles applied. So far no > non-monotonic issue. In the end here's one : preemption latency trace v1.0.5 on 2.6.9-rc1-VP-R1 -------------------------------------------------- latency: 891 us, entries: 38 (38) ----------------- | task: swapper/0, uid:0 nice:0 policy:0 rt_prio:0 ----------------- => started at: do_IRQ+0x19/0x190 => ended at: do_IRQ+0x14a/0x190 =======> 00010000 0.000ms (+0.876ms): do_nmi (robust_get_cycles) 00020000 0.876ms (+0.000ms): profile_tick (nmi_watchdog_tick) 00020000 0.876ms (+0.000ms): profile_hook (profile_tick) 00020001 0.876ms (+0.000ms): notifier_call_chain (profile_hook) 00020000 0.876ms (+689952.730ms): profile_hit (nmi_watchdog_tick) 04000002 689953.607ms (+1.855ms): finish_task_switch (schedule) 00010000 0.877ms (+0.000ms): do_IRQ (default_idle) 00010000 0.877ms (+0.000ms): do_IRQ (<00000000>) 00010001 0.877ms (+0.002ms): mask_and_ack_8259A (do_IRQ) 00010001 0.879ms (+0.000ms): generic_redirect_hardirq (do_IRQ) 00010000 0.880ms (+0.000ms): generic_handle_IRQ_event (do_IRQ) 00010000 0.880ms (+0.000ms): timer_interrupt (generic_handle_IRQ_event) 00010001 0.880ms (+0.005ms): mark_offset_tsc (timer_interrupt) 00010001 0.886ms (+0.000ms): do_timer (timer_interrupt) 00010001 0.886ms (+0.000ms): update_process_times (do_timer) 00010001 0.886ms (+0.000ms): update_one_process (update_process_times) 00010001 0.886ms (+0.000ms): run_local_timers (update_process_times) 00010001 0.886ms (+0.000ms): raise_softirq (update_process_times) 00010001 0.887ms (+0.000ms): scheduler_tick (update_process_times) 00010001 0.887ms (+0.000ms): sched_clock (scheduler_tick) 00010001 0.887ms (+0.000ms): update_wall_time (do_timer) 00010001 0.887ms (+0.000ms): update_wall_time_one_tick (update_wall_time) 00010001 0.888ms (+0.000ms): generic_note_interrupt (do_IRQ) 00010001 0.888ms (+0.000ms): end_8259A_irq (do_IRQ) 00010001 0.888ms (+0.001ms): enable_8259A_irq (do_IRQ) 00000001 0.889ms (+0.000ms): do_softirq (do_IRQ) 00000001 0.889ms (+0.000ms): __do_softirq (do_softirq) 00000001 0.889ms (+0.000ms): wake_up_process (do_softirq) 00000001 0.890ms (+0.000ms): try_to_wake_up (wake_up_process) 00000001 0.890ms (+0.000ms): task_rq_lock (try_to_wake_up) 00000002 0.890ms (+0.000ms): activate_task (try_to_wake_up) 00000002 0.890ms (+0.000ms): sched_clock (activate_task) 00000002 0.890ms (+0.000ms): recalc_task_prio (activate_task) 00000002 0.891ms (+0.000ms): effective_prio (recalc_task_prio) 00000002 0.891ms (+0.000ms): enqueue_task (activate_task) 00000001 0.891ms (+0.000ms): preempt_schedule (try_to_wake_up) 00000001 0.892ms (+0.000ms): sub_preempt_count (do_IRQ) 00000001 0.892ms (+0.000ms): update_max_trace (check_preempt_timing) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/