From: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
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 10:13:29 +0530 [thread overview]
Message-ID: <3f9a31f41002272043t59d18d39ga0296ce3f6602c6d@mail.gmail.com> (raw)
In-Reply-To: <201002272143.22156.rjw@sisk.pl>
Hello Rafael,
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.
Thanks,
--
Jaswinder Singh.
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
> drivers/base/firmware_class.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> Index: linux-2.6.32-SLE11-SP1/drivers/base/firmware_class.c
> ===================================================================
> --- linux-2.6.32-SLE11-SP1.orig/drivers/base/firmware_class.c
> +++ linux-2.6.32-SLE11-SP1/drivers/base/firmware_class.c
> @@ -487,15 +487,14 @@ _request_firmware(const struct firmware
> builtin++) {
> if (strcmp(name, builtin->name))
> continue;
> - dev_info(device, "firmware: using built-in firmware %s\n",
> - name);
> + dev_dbg(device, "firmware: using built-in firmware %s\n", name);
> firmware->size = builtin->size;
> firmware->data = builtin->data;
> return 0;
> }
>
> if (uevent)
> - dev_info(device, "firmware: requesting %s\n", name);
> + dev_dbg(device, "firmware: requesting %s\n", name);
>
> retval = fw_setup_device(firmware, &f_dev, name, device, uevent);
> if (retval)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2010-02-28 4:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 20:43 Rafael J. Wysocki
2010-02-28 3:13 ` Greg KH
2010-02-28 4:43 ` Jaswinder Singh Rajput [this message]
2010-02-28 12:13 ` Rafael J. Wysocki
2010-02-28 16:33 ` Jaswinder Singh Rajput
2010-02-28 19:54 ` Rafael J. Wysocki
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=3f9a31f41002272043t59d18d39ga0296ce3f6602c6d@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®