From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Kravetz Subject: Re: [PATCH RT] tasklet/rt: Prevent tasklets from going into infinite spin in RT Date: Tue, 29 Nov 2011 22:24:31 -0800 Message-ID: <20111130062431.GA2185@monkey.beaverton.ibm.com> References: <1322618120.17003.104.camel@frodo> <20111129215039.344b5109@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Steven Rostedt , LKML , RT , Thomas Gleixner , Ingo Molnar , "Luis Claudio R. Goncalves" To: Clark Williams Return-path: Received: from e6.ny.us.ibm.com ([32.97.182.146]:60647 "EHLO e6.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751317Ab1K3GYq (ORCPT ); Wed, 30 Nov 2011 01:24:46 -0500 Received: from /spool/local by e6.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 30 Nov 2011 01:24:45 -0500 Content-Disposition: inline In-Reply-To: <20111129215039.344b5109@redhat.com> Sender: linux-rt-users-owner@vger.kernel.org List-ID: On Tue, Nov 29, 2011 at 09:50:39PM -0600, Clark Williams wrote: > On Tue, 29 Nov 2011 20:55:20 -0500 > Steven Rostedt wrote: > > > Ingo, > > > > I forward ported this code from 2.6.33.9-rt31, but I think you were the > > original author, as I found most of this code in the > > "tasklet-redesign.patch" from my broken out 2.6.24-rt patches. I > > committed it into my git tree (stable-rt) under your name, and added the > > Signed-off-by that you had in that patch, if you have and objections, > > please let me know. This patch should never see mainline, but it will > > probably be going into the -rt branch. I wrote up this change log, if > > there's something you don't like in it, let me know and I'll fix it. > > > > Luis and Clark (I love saying that), > > No matter how many times you say it, I'm still not treking across the > USA with Luis. :) > > > I booted this patch against 3.0-rt stable, and it didn't crash ;) > > Could you apply it and see if it fixes the hang that you've been seeing. > > Yeah, since Luis is a couple of time zones ahead of us, maybe it'll all > be fixed when we get up in the morning. I've got it running on a system here that frequently encountered the condition. I will let it perform some automated testing while I sleep. Should have results by morning (west coast US). -- Mike