Subject: Re: [Announce] Linux-tiny project revival
From: Joe Perches <joe@perches.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Rob Landley <rob@landley.net>, Indan Zupancic <indan@nul.nu>,
       linux-tiny@selenic.com, Michael Opdenacker <michael@free-electrons.com>,
       CE Linux Developers List <celinux-dev@tree.celinuxforum.org>,
       linux kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <4477DB43-766B-4057-B33D-357A73AF69B0@mac.com>
References: <46F1645D.9050406@am.sony.com>
	 <200709201538.43093.rob@landley.net>
	 <59465.81.207.0.53.1190323573.squirrel@secure.samage.net>
	 <200709201818.42125.rob@landley.net>
	 <4477DB43-766B-4057-B33D-357A73AF69B0@mac.com>
Content-Type: text/plain
Date: Fri, 21 Sep 2007 15:05:34 -0700
Message-Id: <1190412335.32660.55.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 936
Lines: 25

On Fri, 2007-09-21 at 17:34 -0400, Kyle Moffett wrote:
> With a bit more glue that would cause GCC to notice that for a given  
> qprintk_kmalloc the "qpk->type" is always zero because the level is  
> too high, and therefore it would optimize out *ALL* of the  
> _qprintk_kmalloc(), _qprintk(), and _qprintk_finish() calls.

A negative is that lockup conditions swallow partial messages.

Another approach that doesn't require any new buffering is:

id = printk_block_start();
printk_block(id, fmt, ...)
printk_block_end(id)

and have print_block output the id when multiple IDs are
concurrently issued.

This requires a trivial tool to post-process the log
when messages are interleaved.

-
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/