Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752152AbZFWA0B (ORCPT ); Mon, 22 Jun 2009 20:26:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753260AbZFWAZx (ORCPT ); Mon, 22 Jun 2009 20:25:53 -0400 Received: from gate.crashing.org ([63.228.1.57]:34729 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754659AbZFWAZw (ORCPT ); Mon, 22 Jun 2009 20:25:52 -0400 Subject: Re: [git pull] drm: previous pull req + 1. From: Benjamin Herrenschmidt To: Linus Torvalds Cc: Thomas =?ISO-8859-1?Q?Hellstr=F6m?= , Dave Airlie , Alex Deucher , Andrew Lutomirski , dri-devel@lists.sf.net, Jerome Glisse , Linux Kernel Mailing List In-Reply-To: References: <4A3DABE1.50309@mit.edu> <4A3F3E3A.2030202@shipmail.org> Content-Type: text/plain Date: Tue, 23 Jun 2009 10:01:39 +1000 Message-Id: <1245715299.4017.15.camel@pasglop> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 976 Lines: 28 On Mon, 2009-06-22 at 11:22 -0700, Linus Torvalds wrote: > Not going to happen. > > Why? 'printk'. > > If you can't handle printk, then you're basically useless. And printk > absolutely -has- to work in bad situations (the most important > messages could happen in any context). Well... yes and no. If X is frontmost, printk is not going to be printed, ie, I'm talking about today, when the console is !KD_TEXT. There -is- a mechanism to deal with these things today, and the console semaphore does take care of accesses to the fb. (That doesn't exclude having the ability to force-switch back to kernel fb for printing things like oops btw, which KMS could do, but for basic access control, it makes sense). Cheers, Ben. -- 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/