Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934569AbZJIV4J (ORCPT ); Fri, 9 Oct 2009 17:56:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S934544AbZJIV4I (ORCPT ); Fri, 9 Oct 2009 17:56:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:9547 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934529AbZJIV4G (ORCPT ); Fri, 9 Oct 2009 17:56:06 -0400 Date: Fri, 9 Oct 2009 17:55:21 -0400 (EDT) From: John Kacur To: Arnd Bergmann Cc: tglx@linutronix.de, Ingo Molnar , linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org, Clark Williams Message-ID: <571973584.1452471255125321659.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> In-Reply-To: <1033457751.1452271255124941735.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Subject: Re: [PATCH RFC] BKL not necessary in cpuid_open MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.5.5.72] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1678 Lines: 44 ----- "Arnd Bergmann" wrote: > On Wednesday 07 October 2009, John Kacur wrote: > > > > I've been staring at the BKL lock in cpuid_open, and I can't see > what it > > is protecting. However, I may have missed something - even something > > > obvious, so comments are welcome. > > > > Hi John, > > In general, the lock_kernel() calls in any chardev open() file > operation > are the result of the BKL pushdown by Jon Corbet and others, which has > happened > some time last year[1]. I'd assume that the vast majority is not > needed > at all, so these are an easy target for removal. > > Arnd > > [1] http://lkml.indiana.edu/hypermail/linux/kernel/0805.2/0257.html yup - I'm aware of all the hard work that many people put in before I ever looked at this. Thomas asked the -rt folks to have a look at removing the bkl look during the rt-mini summit in Dresden. I was looking for low hanging fruit to get started. The confusion was over what was already implemented in tip/rt/bkl. I merely looked at the latest linus/master build. The result was a good one though, because basically Thomas' work got pushed from tip/rt/bkl into tip/master, and can hopefully be pushed upstream during the next merge window. Even if getting starting means just reviewing what is in rt/bkl and not yet in linus/master, I think that would be positive. I'm sure Thomas will stomp on me if I start to annoy him. :) Thanks John -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/