From owner-freebsd-smp Mon Mar 25 11:15:54 2002 Delivered-To: freebsd-smp@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id 0559B37B64A; Mon, 25 Mar 2002 11:15:12 -0800 (PST) Received: from mailgate.nlsystems.com ([62.49.251.130] helo=herring.nlsystems.com) by anchor-post-32.mail.demon.net with esmtp (Exim 3.35 #1) id 16pZvy-000DUn-0W; Mon, 25 Mar 2002 19:15:10 +0000 Received: from salmon.nlsystems.com (salmon [10.0.0.3]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id g2PJDt948041; Mon, 25 Mar 2002 19:13:55 GMT (envelope-from dfr@nlsystems.com) Date: Mon, 25 Mar 2002 19:10:22 +0000 (GMT) From: Doug Rabson To: John Baldwin Cc: Jake Burkholder , , Andy Isaacson Subject: printf locking (was Re: FreeBSD 4.5: Second CPU Not Working on Dell PowerEdge 1650) In-Reply-To: Message-ID: <20020325190742.B99274-100000@salmon.nlsystems.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 25 Mar 2002, John Baldwin wrote: > > Hmmmm. Well, we really need proper printf locking (which probably shouldn't > use blocking locks). Weren't there some patches (from chuckp?) floating around to do this. Something along the lines of a trylock which buffers characters somewhere if it fails. I wanted this (again) recently - I couldn't work out why syscons kept wedging until I remembered there were no locks on the console. In the end, I just switched to a serial console. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message