linux-kernel - Re: Dynamic Debug module.ddebug fake param enhancements V4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201009270909.18490.bjorn.helgaas@hp.com>
Date:	Mon, 27 Sep 2010 09:09:18 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Thomas Renninger <trenn@...e.de>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org, jbaron@...hat.com
Subject: Re: Dynamic Debug module.ddebug fake param enhancements V4

On Monday, September 27, 2010 02:25:46 am Thomas Renninger wrote:

> What do you think (dev_dbg vs printk(KERN_DEBUG...)?

Well, 99% of the time, what I want is simply the resource usage of all
the devices in the system.  Currently, a dmesg log gives me that for
PCI devices.  I plan to change PNP so the dmesg log will also contain
that for PNP devices.  That's simple and requires no user action at all
and no extra boots.

The times when we need more extensive debugging are rare enough that
I'm not sure it's worth keeping them compiled into the kernel, even
if they are turned off by default (I understand the tradeoff from
a distro point of view might be different).

With the exception of the ones in pnp/resource.c that I want to convert
to dev_printk(KERN_DEBUG), I think all the pnp_dbg() uses are things
I used during PNP development and haven't ever needed since.

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