Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752116AbZKSM5p (ORCPT ); Thu, 19 Nov 2009 07:57:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751468AbZKSM5o (ORCPT ); Thu, 19 Nov 2009 07:57:44 -0500 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:52035 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751369AbZKSM5n (ORCPT ); Thu, 19 Nov 2009 07:57:43 -0500 Date: Thu, 19 Nov 2009 12:59:06 +0000 From: Alan Cox To: Jean Delvare Cc: Thomas Gleixner , Leon Woestenberg , Mark Brown , Sven-Thorsten Dietrich , linux-i2c@vger.kernel.org, rt-users , "Ben Dooks (embedded platforms)" , Peter Zijlstra , LKML Subject: Re: yield() in i2c non-happy paths hits BUG under -rt patch Message-ID: <20091119125906.6ad00edd@lxorguk.ukuu.org.uk> In-Reply-To: <20091119130526.23a69b85@hyperion.delvare> References: <20091107210147.3e754278@hyperion.delvare> <4AF7148C.9090706@thebigcorporation.com> <20091112211255.09cd884a@hyperion.delvare> <20091116155606.GC29479@sirena.org.uk> <20091118010520.4cd397d4@lxorguk.ukuu.org.uk> <20091118175202.490989d8@hyperion.delvare> <20091119130526.23a69b85@hyperion.delvare> X-Mailer: Claws Mail 3.7.3 (GTK+ 2.14.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 600 Lines: 15 > Well, I guess only people monitoring system latency would notice, as > this is the only thing yield() was supposed to help with in the first > place. if (need_resched()) schedule(); will make non-rt tasks act politely at the right moments. RT tasks will likely immediately get to take the CPU again depending upon the scheduling parameters in use. -- 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/