From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750768AbWFAVtK (ORCPT ); Thu, 1 Jun 2006 17:49:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750800AbWFAVtK (ORCPT ); Thu, 1 Jun 2006 17:49:10 -0400 Received: from nz-out-0102.google.com ([64.233.162.196]:50146 "EHLO nz-out-0102.google.com") by vger.kernel.org with ESMTP id S1750768AbWFAVtI (ORCPT ); Thu, 1 Jun 2006 17:49:08 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=udbalEiOjmTWnmbbepUBhDlZmHxC4APRA/oJwtndt8X5XqR3OF8fEYEbd02VAws/WtPylEMYwy1F6jYqg4PUZskCpTyrHXAkbbMU93faug9OOSYSw7wC/cCW9cQkFh98ZJ2vRpn6dxpTTG9D5O2f3CK1jf7K0XLWcJz/EMPdyzU= Message-ID: <9e4733910606011448x32246dfcy2a2d448e238bdab3@mail.gmail.com> Date: Thu, 1 Jun 2006 17:48:57 -0400 From: "Jon Smirl" To: "Antonino A. Daplas" Subject: Re: OpenGL-based framebuffer concepts Cc: "D. Hazelton" , "David Lang" , "Ondrej Zajicek" , "Dave Airlie" , "Pavel Machek" , "Alan Cox" , "Kyle Moffett" , "Manu Abraham" , "linux cbon" , "Helge Hafting" , Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org In-Reply-To: <447F5CB3.7000107@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060519224056.37429.qmail@web26611.mail.ukl.yahoo.com> <9e4733910606010959o4f11d7cfp2d280c6f2019cccf@mail.gmail.com> <200606011603.57421.dhazelton@enter.net> <9e4733910606011335q5791997drc02d23f398a2acf5@mail.gmail.com> <447F56A0.8030408@gmail.com> <9e4733910606011423u75fa076hce22547c28c0a987@mail.gmail.com> <447F5CB3.7000107@gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 6/1/06, Antonino A. Daplas wrote: > Jon Smirl wrote: > > On 6/1/06, Antonino A. Daplas wrote: > >> Jon Smirl wrote: > >> > On 6/1/06, D. Hazelton wrote: > >> > > >> > >> Console writes are done with the console semaphore held. printk will also > >> just write to the log buffer and defer the actual console printing > >> for later, by the next or current process that will grab the semaphore. > > > > That was my original position too. But Alan Cox has drilled it into me > > that this is not acceptable for printks in interrupt context, they > > need to print there and not be deferred. > > > > Just to clarify, it's not my position, that's how the current printk code > works. I haven't looked at the code, but if there is just normal console running and nothing like X is around, doesn't the console system always have the semaphore? If it always has the semaphore then interupt context printk's aren't blocked. I think that interrupt context printk's work today, I have definitely seen one printk get inserted into the middle of another on my console. How else could you achieve that? -- Jon Smirl jonsmirl@gmail.com