Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751694AbaAOKr3 (ORCPT ); Wed, 15 Jan 2014 05:47:29 -0500 Received: from mail-ob0-f176.google.com ([209.85.214.176]:56441 "EHLO mail-ob0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751004AbaAOKr0 (ORCPT ); Wed, 15 Jan 2014 05:47:26 -0500 MIME-Version: 1.0 In-Reply-To: <20140115103808.GY31570@twins.programming.kicks-ass.net> References: <20140115103808.GY31570@twins.programming.kicks-ass.net> Date: Wed, 15 Jan 2014 16:17:26 +0530 Message-ID: Subject: Re: [QUERY]: Is using CPU hotplug right for isolating CPUs? From: Viresh Kumar To: Peter Zijlstra Cc: =?ISO-8859-1?Q?Fr=E9d=E9ric_Weisbecker?= , Kevin Hilman , Vincent Guittot , Amit Kucheria , Lists linaro-kernel , Linaro Networking , Linux Kernel Mailing List , Steven Rostedt Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15 January 2014 16:08, Peter Zijlstra wrote: > Nah, its just ugly and we should fix it. You need to be careful to not > place tasks in a cpuset you're going to unplug though, that'll give > funny results. Okay. So how do you suggest to get rid of cases like a work queued on CPU1 initially and because it gets queued again from its work handler, it stays on the same CPU forever. And then there were timer overflow events that occur because hrtimer is started by tick-sched stuff for 450 seconds later in time. -- viresh -- 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/