From: Michael Ellerman <michael@ellerman.id.au>
To: Greg KH <greg@kroah.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Matthew Wilcox <matthew@wil.cx>,
linux-pci <linux-pci@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: more than 50 percent of dmesg belongs only to PCI and USB
Date: Mon, 16 Mar 2009 11:59:21 +1100 [thread overview]
Message-ID: <1237165161.8619.19.camel@localhost> (raw)
In-Reply-To: <20090316003932.GB15098@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
On Sun, 2009-03-15 at 17:39 -0700, Greg KH wrote:
> On Mon, Mar 16, 2009 at 10:28:49AM +1100, Michael Ellerman wrote:
> > On Sat, 2009-03-14 at 13:11 +0530, Jaswinder Singh Rajput wrote:
> > > Can we make dmesg little bit better and remove some noise and put these
> > > debug messages on /sys/kernel/debug/ :
> >
> > I think they should just be KERN_DEBUG, that way they won't be displayed
> > to most users, except people who want to see them.
> >
> > The problem is it's easier to write:
> >
> > dev_info(&dev->dev, "transparent bridge\n");
> >
> > than:
> >
> > dev_printk(KERN_DEBUG, &dev->dev, "transparent bridge\n");
> >
> > and, dev_dbg() does not do what you want in this case.
>
> Why not? It prints it out if you enable the config option at run-time,
> which is what you want.
Only if you have CONFIG_DYNAMIC_PRINTK_DEBUG or whatever it's called
enabled. Which is a terrible idea because it compiles-in all the
pr_debug() and dev_dbg() code that used to be if (0)'ed.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-03-16 0:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 7:41 more than 50 percent of dmesg belongs only to PCI and USB Jaswinder Singh Rajput
2009-03-14 15:41 ` Greg KH
2009-03-15 23:28 ` Michael Ellerman
2009-03-16 0:39 ` Greg KH
2009-03-16 0:59 ` Michael Ellerman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1237165161.8619.19.camel@localhost \
--to=michael@ellerman.id.au \
--cc=greg@kroah.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox