This series adds a configuration option to selectively compile out
printk message strings based on a verbosity level.
This works by wrapping printk with a macro which evaluates to a
constant if condition which the compiler will be able to optimize
out.
However because printk might be wrapped
Because printk might be wrapped by a macro avoid constructs which
assume that the return value can be interpreted as a boolean value.
This doesn't work because the macro has no return value which
results in a compile error void value not ignored as it ought to be.
Signed-off-by: Marc Andre
Introduce a config option which allows to selectively compile out
printk messages based on a specified verbosity level.
Signed-off-by: Marc Andre Tanner m...@brain-dump.org
---
init/Kconfig | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git
Don't rely on the return value of STK_ERROR which is a wrapper
around printk use a normal if clause instead.
Signed-off-by: Marc Andre Tanner m...@brain-dump.org
---
drivers/media/video/stk-webcam.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git
Use the unfiltered variant in cases where the return value
is of interest.
Signed-off-by: Marc Andre Tanner m...@brain-dump.org
---
drivers/char/mem.c |2 +-
drivers/md/md.c|2 +-
drivers/scsi/aic7xxx/aic79xx_osm.h |2 +-
A later patch will #undef printk because the macro would otherwise
conflict with the function definition. Moving the printk function
to the end of the file makes sure that the macro is expanded within
the rest of the file.
Signed-off-by: Marc Andre Tanner m...@brain-dump.org
---
kernel/printk.c
The standard printk function will be wrapped by a macro.
However this doesn't work in all situations (for example
when the return value of printk is of interest). We
therefore provide a new function which is just an alias
to printk and therefore bypasses the macro.
Signed-off-by: Marc Andre
Marc Andre Tanner wrote:
+ * The check with sizeof(void*) should make sure that we don't operate on
+ * pointers, which the compiler wouldn't be able to optimize out, but only
+ * on string constants.
Take a look at __builtin_constant_p in the GCC manual.
You'll probably find that wrapping
On Tue, Sep 1, 2009 at 18:31, Marc Andre Tanner wrote:
This series adds a configuration option to selectively compile out
printk message strings based on a verbosity level.
This works by wrapping printk with a macro which evaluates to a
constant if condition which the compiler will be able to
On Tuesday, September 01, 2009 4:24 PM, Tim Bird wrote:
Marc Andre Tanner wrote:
The macro filters out printk messages based on a configurable verbosity
level (CONFIG_PRINTK_VERBOSITY).
Signed-off-by: Marc Andre Tanner m...@brain-dump.org
---
include/linux/kernel.h | 24
On Thu, Aug 20, 2009 at 12:50 AM, Johannes Stezenbach j...@sig21.net wrote:
Hi,
a while ago I was working on a SoC with 200MHz ARM926EJ-S CPU
and integrated 100Mbit ethernet core, connected on internal
(fast) memory bus, with DMA. With iperf I measured:
TCP RX ~70Mbit/sec (iperf -s on
11 matches
Mail list logo