From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754958AbaDNLwd (ORCPT ); Mon, 14 Apr 2014 07:52:33 -0400 Received: from mail-oa0-f54.google.com ([209.85.219.54]:35692 "EHLO mail-oa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754160AbaDNLwa (ORCPT ); Mon, 14 Apr 2014 07:52:30 -0400 MIME-Version: 1.0 In-Reply-To: <20140414114744.GI11096@twins.programming.kicks-ass.net> References: <20140410143857.GA27654@localhost.localdomain> <20140411145333.GC3438@localhost.localdomain> <20140411151825.GX11096@twins.programming.kicks-ass.net> <20140414110245.GG11096@twins.programming.kicks-ass.net> <20140414114744.GI11096@twins.programming.kicks-ass.net> Date: Mon, 14 Apr 2014 17:22:30 +0530 Message-ID: Subject: Re: [Query]: tick-sched: why don't we stop tick when we are running idle task? From: Viresh Kumar To: Peter Zijlstra Cc: Frederic Weisbecker , Thomas Gleixner , Linux Kernel Mailing List , Lists linaro-kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14 April 2014 17:17, Peter Zijlstra wrote: > What causes this tick? I was under the impression that once there's a > single task (not doing any syscalls) and the above issues are sorted, no > more tick would happen. This is what Frederic told me earlier: https://lkml.org/lkml/2014/2/13/238