From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267356AbUGNKaw (ORCPT ); Wed, 14 Jul 2004 06:30:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267357AbUGNKaw (ORCPT ); Wed, 14 Jul 2004 06:30:52 -0400 Received: from cantor.suse.de ([195.135.220.2]:31886 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S267356AbUGNKan (ORCPT ); Wed, 14 Jul 2004 06:30:43 -0400 Date: Wed, 14 Jul 2004 12:29:43 +0200 Message-ID: From: Takashi Iwai To: Lenar =?ISO-8859-1?Q?L=F5hmus?= Cc: William Lee Irwin III , linux-kernel@vger.kernel.org Subject: Re: preempt-timing-2.6.8-rc1 In-Reply-To: <40F4E7F9.3020603@vision.ee> References: <20040713122805.GZ21066@holomorphy.com> <40F3F0A0.9080100@vision.ee> <20040713143947.GG21066@holomorphy.com> <40F40080.8010801@vision.ee> <20040713221654.GJ21066@holomorphy.com> <40F4E7F9.3020603@vision.ee> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 15) (Security Through Obscurity) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At Wed, 14 Jul 2004 10:59:53 +0300, Lenar Lõhmus wrote: > > And this still seems to be very long and real: > 50ms non-preemptible critical section violated 2 ms preempt threshold > starting at snd_pcm_action_lock_irq+0x1b/0x1d0 [snd_pcm] and ending at > snd_pcm_action_lock_irq+0x65/0x1d0 [snd_pcm] > Trace has this: > [] snd_pcm_playback_ioctl1+0x49/0x2f0 [snd_pcm] > So maybe this too is ioctl related (non-educated guess)? If it's SNDRV_PCM_IOCTL_PREPARE, I'm modifying the relevant code with rwsem instead of rwlock. But it's still in BKL of ioctl. Do we need to unlock internally? Takashi