From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758651AbYAHDdm (ORCPT ); Mon, 7 Jan 2008 22:33:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753957AbYAHDdc (ORCPT ); Mon, 7 Jan 2008 22:33:32 -0500 Received: from ns1.suse.de ([195.135.220.2]:53021 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753483AbYAHDdb (ORCPT ); Mon, 7 Jan 2008 22:33:31 -0500 Date: Tue, 8 Jan 2008 04:33:30 +0100 From: Andi Kleen To: Steven Rostedt Cc: LKML , Linus Torvalds , Andrew Morton , Ingo Molnar , Thomas Gleixner , Andi Kleen , "Brown, Len" , Venkatesh Pallipadi , Adam Belay , Peter Zijlstra Subject: Re: [RFC PATCH] kick sleeping idle CPUS on cpu_idle_wait Message-ID: <20080108033329.GI2998@bingen.suse.de> References: <1199759244.26343.35.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1199759244.26343.35.camel@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 07, 2008 at 09:27:24PM -0500, Steven Rostedt wrote: > > Sometimes cpu_idle_wait gets stuck because it might miss CPUS that are > already in idle, have no tasks waiting to run and have no interrupts > going to them. This is common on bootup when switching cpu idle > governors. I must admit I never liked that cpu idle wait code anyways. Why again can't normal RCU be used for this? Waiting for two RCU quiescent cycles should be enough, shouldn't it? -Andi