[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2628z6euk.fsf@firstfloor.org>
Date: Fri, 03 Aug 2012 10:54:27 -0700
From: Andi Kleen <andi@...stfloor.org>
To: Vikram Pandita <vikram.pandita@...com>
Cc: <gregkh@...uxfoundation.org>, <kay@...y.org>,
<linux-kernel@...r.kernel.org>, <linux-omap@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Mike Turquette <mturquette@...aro.org>,
Vimarsh Zutshi <vimarsh.zutshi@...il.com>
Subject: Re: [PATCH v3] printk: add option to print cpu id
Vikram Pandita <vikram.pandita@...com> writes:
> From: Vikram Pandita <vikram.pandita@...com>
>
> Introduce config option to enable CPU id reporting for printk() calls.
What's wrong with using trace_printk for this? That's much faster
anyways. Generally printk is so slow that it's typically useless for
instrumenting races.
And really: Wasting 1/3 of the 80 character line is too much.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists