From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261993AbVHCCmf (ORCPT ); Tue, 2 Aug 2005 22:42:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261997AbVHCCmf (ORCPT ); Tue, 2 Aug 2005 22:42:35 -0400 Received: from ms-smtp-03.nyroc.rr.com ([24.24.2.57]:43416 "EHLO ms-smtp-03.nyroc.rr.com") by vger.kernel.org with ESMTP id S261993AbVHCCme (ORCPT ); Tue, 2 Aug 2005 22:42:34 -0400 Subject: Re: [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.52-01 From: Steven Rostedt To: Daniel Walker Cc: Ingo Molnar , linux-kernel@vger.kernel.org In-Reply-To: <1123035909.11101.1.camel@c-67-188-6-232.hsd1.ca.comcast.net> References: <20050730160345.GA3584@elte.hu> <1122920564.6759.15.camel@localhost.localdomain> <1122931238.4623.17.camel@dhcp153.mvista.com> <1122944010.6759.64.camel@localhost.localdomain> <20050802101920.GA25759@elte.hu> <1123011928.1590.43.camel@localhost.localdomain> <1123025895.25712.7.camel@dhcp153.mvista.com> <1123027226.1590.59.camel@localhost.localdomain> <1123035909.11101.1.camel@c-67-188-6-232.hsd1.ca.comcast.net> Content-Type: text/plain Organization: Kihon Technologies Date: Tue, 02 Aug 2005 22:42:16 -0400 Message-Id: <1123036936.1590.69.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2005-08-02 at 19:25 -0700, Daniel Walker wrote: > On Tue, 2005-08-02 at 20:00 -0400, Steven Rostedt wrote: > > On Tue, 2005-08-02 at 16:38 -0700, Daniel Walker wrote: > > > Couldn't you just do some math off current->timestamp to see how long > > > the task has been running? This per arch stuff seems a bit invasive.. > > > > The thing is, I'm tracking how long the task is running in the kernel > > without doing a schedule. That's actually easy, but I don't want to > > Why make the distinction ? For what I was going for all I wanted to know > was that an RT task was eating up all the CPU . Did you have something > else in mind? Yeah, bugs in the kernel :-) I can change the patch to just see who is hogging the CPU for more than X amount of seconds (10 by default) if that pleases everyone. If that's what people want, then I'll send another patch tomorrow. If this is the way to go, then I'll add back the check for RT tasks to limit the output to just RT hogs. Or is any hog OK? I guess this would at least keep it arch independent. Although I like my little hack with the additions to thread_info and entry.S ;-) -- Steve