From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933025AbbBQIf3 (ORCPT ); Tue, 17 Feb 2015 03:35:29 -0500 Received: from www.linutronix.de ([62.245.132.108]:42673 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933007AbbBQIf0 (ORCPT ); Tue, 17 Feb 2015 03:35:26 -0500 Date: Tue, 17 Feb 2015 09:35:24 +0100 From: Sebastian Andrzej Siewior To: Andrey Smirnov Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org, asmirnov@kymetacorp.com, panos@kymetacorp.com Subject: Re: i.MX6, PREEMPT-RT and interactive cpufreq governor Message-ID: <20150217083523.GA26177@linutronix.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Key-Id: 97C4700B X-Key-Fingerprint: 09E2 D1F3 9A3A FF13 C3D3 961C 0688 1C1E 97C4 700B User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Andrey Smirnov | 2014-06-10 11:52:05 [-0700]: >Eventually I am hoping to disable any sorts of frequency scaling or >power management on our system, but I am still curious to know if that >is a known issue patches for which exist. Does anyone has any leads/suggestions? You need to breakout of the preempt_disable() region. However having cpufreq running will have major effect on your latency so this might not what you want in the long term. >Thank you, >Andrey Smirnov Sebastian