From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [patch] rt: sysprof hrtimer fix Date: Fri, 13 Feb 2009 13:49:28 +0100 Message-ID: <20090213124928.GC5483@elte.hu> References: <20090213004812.GA5824@nowhere> <20090213021626.GA5807@nowhere> <20090213030919.GA5826@nowhere> <20090213072601.GA26946@elte.hu> <20090213120451.GA5782@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Thomas Gleixner , Thomas Gleixner , LKML , rt-users , Steven Rostedt , Peter Zijlstra , Carsten Emde , Clark Williams To: Frederic Weisbecker Return-path: Received: from mx2.mail.elte.hu ([157.181.151.9]:45083 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752824AbZBMMtw (ORCPT ); Fri, 13 Feb 2009 07:49:52 -0500 Content-Disposition: inline In-Reply-To: <20090213120451.GA5782@nowhere> Sender: linux-rt-users-owner@vger.kernel.org List-ID: * Frederic Weisbecker wrote: > So, just a thing. > -rt make the hrtimer's timers running on softirq context because the hrtimer_interrupt > doesn't run as a threaded interrupt, and then it is not preemptible right? > > In that case, sysprof will continue to run in hardirq context, as before, and > it will considerably increase the latency. And that matters here. > So I think it is important to put it on the reminder: hm, not sure. Do you know it numerically how much worst-case overhead it induces? Ingo