Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753471AbaKJQVR (ORCPT ); Mon, 10 Nov 2014 11:21:17 -0500 Received: from resqmta-ch2-02v.sys.comcast.net ([69.252.207.34]:39622 "EHLO resqmta-ch2-02v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752886AbaKJQVN (ORCPT ); Mon, 10 Nov 2014 11:21:13 -0500 Date: Mon, 10 Nov 2014 10:21:11 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: "Paul E. McKenney" cc: Viresh Kumar , Thomas Gleixner , Frederic Weisbecker , Linux Kernel Mailing List , Gilad Ben-Yossef , Tejun Heo , John Stultz , Mike Frysinger , Minchan Kim , Hakan Akkan , Max Krasnyansky , Hugh Dickins , "H. Peter Anvin" , Ingo Molnar , Peter Zijlstra Subject: Re: [NOHZ] Remove scheduler_tick_max_deferment In-Reply-To: <20141110153147.GK4901@linux.vnet.ibm.com> Message-ID: References: <20141110153147.GK4901@linux.vnet.ibm.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 10 Nov 2014, Paul E. McKenney wrote: > Would it make sense for unlimited max deferment to be available as > a boot parameter? That would allow people who want tick-free execution > more than accurate stats to get that easily, while keeping stats accurate > for everyone else. Well at least it would help us to get started on figuring out how to deal with other processor interruptions that occur in intervals of seconds or minutes. -- 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/