[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6c5249afad274ce49e643d9b05706e3a@AcuMS.aculab.com>
Date: Fri, 21 Aug 2020 12:18:28 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Nicolas Boichat' <drinkcat@...omium.org>
CC: Steven Rostedt <rostedt@...dmis.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Andy Shevchenko" <andriy.shevchenko@...ux.intel.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
lkml <linux-kernel@...r.kernel.org>,
"Linux Media Mailing List" <linux-media@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Josh Poimboeuf <jpoimboe@...hat.com>
Subject: RE: [PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed
From: Nicolas Boichat
> Sent: 21 August 2020 13:07
...
> > You might also want a #define that can set temporarily
> > to enable traces in a specific file/module even though
> > CONFIG_TRACE=n.
>
> I don't understand how traces are supposed to work with CONFIG_TRACE=n?
Probably because I meant something different :-)
You want the kernel built so that there are no (expanded)
calls to trace_printf() but with support for modules that
contain them.
Then I can load a module into a distro kernel that
contains trace_printf() calls for debug testing.
Which is why I was suggesting a config option that
only rand-config builds would ever set that would
cause the calls to generate compile-time errors.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists