Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752298AbaAPJqj (ORCPT ); Thu, 16 Jan 2014 04:46:39 -0500 Received: from www.linutronix.de ([62.245.132.108]:34313 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751325AbaAPJqe (ORCPT ); Thu, 16 Jan 2014 04:46:34 -0500 Date: Thu, 16 Jan 2014 10:46:22 +0100 (CET) From: Thomas Gleixner To: Viresh Kumar cc: Frederic Weisbecker , Peter Zijlstra , Linux Kernel Mailing List , Lists linaro-kernel , Steven Rostedt , Linaro Networking Subject: Re: [QUERY]: Is using CPU hotplug right for isolating CPUs? In-Reply-To: Message-ID: References: <20140115171704.GB21574@localhost.localdomain> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 16 Jan 2014, Viresh Kumar wrote: > On 15 January 2014 22:47, Frederic Weisbecker wrote: > > Are you sure about that? NO_HZ_FULL shouldn't touch much hrtimers. > > Those are independant from the tick. > > > > Although some of them seem to rely on the softirq, but that seem to > > concern the tick hrtimer only. > > To make it clear I was talking about the hrtimer used by tick_sched_timer. > I have crossed checked which timers are active on isolated CPU from > /proc/timer_list and it gave on tick_sched_timer's hrtimer. > > In the attached trace (dft.txt), see these locations: > - Line 252: Time 302.573881: we scheduled the hrtimer for 300 seconds > ahead of current time. > - Line 254, 258, 262, 330, 334: We got interruptions continuously after > ~90 seconds and this looked to be a case of timer's counter overflow. > Isn't it? (I have removed some lines towards the end of this file to make > it shorter, though dft.dat is untouched) Just do the math. max reload value / timer freq = max time span So: 0x7fffffff / 24MHz = 89.478485 sec Nothing to do here except to get rid of the requirement to arm the timer at all. Thanks, tglx -- 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/