From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Greg KH <gregkh@suse.de>, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Driver core: Reduce the level of request_firmware() messages
Date: Sun, 28 Feb 2010 20:54:32 +0100 [thread overview]
Message-ID: <201002282054.32204.rjw@sisk.pl> (raw)
In-Reply-To: <1267374785.1929.2.camel@i7.satnam>
On Sunday 28 February 2010, Jaswinder Singh Rajput wrote:
> Hello Rafael,
>
> On Sun, 2010-02-28 at 13:13 +0100, Rafael J. Wysocki wrote:
> > On Sunday 28 February 2010, Jaswinder Singh Rajput wrote:
> > > On Sun, Feb 28, 2010 at 2:13 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > > > From: Rafael J. Wysocki <rjw@sisk.pl>
> > > >
> > > > The messages from _request_firmware() informing that firmware is
> > > > being requested or built-in firmware is going to be used are printed
> > > > at KERN_INFO, which produces lots of noise on systems with huge
> > > > numbers of AMD CPUs. Reduce the level of these messages to
> > > > KERN_DEBUG to get rid of that noise.
> > > >
> > >
> > > Which firmware we are using is very useful information. Because of
> > > huge numbers of CPUs it seems noise then better provide the
> > > information for first cpu and for the rest of the CPUs you can show by
> > > KERN_DEBUG.
> >
> > That would have been better indeed, but the problem is _request_firmware()
> > doesn't allow us to change the level of its messages on demand.
>
> Can we try this :
>
> if (smp_processor_id())
> dev_dbg(..);
> else
> dev_info(..);
Well, it doesn't look particularly nice, does it?
Besides, say we're requesting firmware for a non-CPU device which happens
to run on CPU1. Then, dev_dbg() will be used, which most likely is not what we
want.
Rafael
next prev parent reply other threads:[~2010-02-28 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 20:43 [PATCH] Driver core: Reduce the level of request_firmware() messages Rafael J. Wysocki
2010-02-28 3:13 ` Greg KH
2010-02-28 4:43 ` Jaswinder Singh Rajput
2010-02-28 12:13 ` Rafael J. Wysocki
2010-02-28 16:33 ` Jaswinder Singh Rajput
2010-02-28 19:54 ` Rafael J. Wysocki [this message]
2010-02-28 20:13 ` Jaswinder Singh Rajput
2010-03-15 20:16 ` Greg KH
2010-03-15 21:27 ` Rafael J. Wysocki
2010-03-15 23:34 ` Jaswinder Singh Rajput
2010-03-15 23:40 ` Rafael J. Wysocki
2010-03-15 23:55 ` Jaswinder Singh Rajput
2010-03-15 23:44 ` Greg KH
2010-03-16 0:17 ` Rafael J. Wysocki
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=201002282054.32204.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@suse.de \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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