Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754493Ab2B0SVZ (ORCPT ); Mon, 27 Feb 2012 13:21:25 -0500 Received: from mail-gy0-f174.google.com ([209.85.160.174]:55980 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754163Ab2B0SVY (ORCPT ); Mon, 27 Feb 2012 13:21:24 -0500 Authentication-Results: mr.google.com; spf=pass (google.com: domain of venki@google.com designates 10.50.189.200 as permitted sender) smtp.mail=venki@google.com; dkim=pass header.i=venki@google.com MIME-Version: 1.0 In-Reply-To: <20120227073239.GA3397@elte.hu> References: <1330122800-834-1-git-send-email-venki@google.com> <20120227073239.GA3397@elte.hu> Date: Mon, 27 Feb 2012 10:21:23 -0800 Message-ID: Subject: Re: [PATCH 0/4] Extend mwait idle to optimize away CAL and RES interrupts to an idle CPU -v2 From: Venki Pallipadi To: Ingo Molnar Cc: Peter Zijlstra , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Suresh Siddha , Aaron Durbin , Paul Turner , Yong Zhang , Andi Kleen , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 865 Lines: 24 On Sun, Feb 26, 2012 at 11:32 PM, Ingo Molnar wrote: > > * Venkatesh Pallipadi wrote: > >> [...] I did have to avoid x86 smpboot cleanup that Ingo >> suggested as that did not seem trivial to me :-). > > Well, idletask_ti_flags is unacceptably ugly, please do the > smpboot.c cleanup because that paves the way to add new features > to the x86 idle code. > OK. Will look at this soon. If everything else looks OK, can you queue up the first 3 patches in the series somewhere so that it gets some wider testing. Things should work without that idletask_ti_flags change. Thanks, Venki -- 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/