From: Bjorn Helgaas <bhelgaas@google.com>
To: Nathan Zimmer <nzimmer@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] revert "PCI: log vendor/device ID always"
Date: Wed, 3 Oct 2012 16:54:09 -0600 [thread overview]
Message-ID: <CAErSpo7ZQEm9==nsGiH2c_ZG8LPP8MAA8M9xSPyWPtCW2EHUUQ@mail.gmail.com> (raw)
In-Reply-To: <1349187780-25692-1-git-send-email-nzimmer@sgi.com>
On Tue, Oct 2, 2012 at 8:23 AM, Nathan Zimmer <nzimmer@sgi.com> wrote:
> Revert commit id 2c6413aee215a43b1f95e218067abcde50ccbc5e
> On larger systems (256 cores+) with signifigant IO attached this single message
> represents over 20% of the messages at boot.
Is this causing a problem? The messages are at KERN_DEBUG, so they
shouldn't be going to the console by default anyway.
I/O devices normally have at least one BAR, as well as some PME
messages, so a change like this won't affect them too much. My guess
is that it's really the large number of CPUs, where we find all the
uncore/memory controller/etc stuff where this is a problem. Those
devices don't have BARs, so
this line is probably the only information about them in dmesg.
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
>
> Signed-off-by: Nathan Zimmer <nzimmer@sgi.com>
> ---
> drivers/pci/probe.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index 9f8a6b7..a1add54 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -1002,8 +1002,8 @@ int pci_setup_device(struct pci_dev *dev)
> dev->revision = class & 0xff;
> dev->class = class >> 8; /* upper 3 bytes */
>
> - dev_printk(KERN_DEBUG, &dev->dev, "[%04x:%04x] type %02x class %#08x\n",
> - dev->vendor, dev->device, dev->hdr_type, dev->class);
> + dev_dbg(&dev->dev, "[%04x:%04x] type %02x class %#08x\n",
> + dev->vendor, dev->device, dev->hdr_type, dev->class);
>
> /* need to have dev->class ready */
> dev->cfg_size = pci_cfg_space_size(dev);
> --
> 1.6.0.2
>
next parent reply other threads:[~2012-10-03 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1349187780-25692-1-git-send-email-nzimmer@sgi.com>
2012-10-03 22:54 ` Bjorn Helgaas [this message]
2012-10-04 16:02 ` [PATCH] revert "PCI: log vendor/device ID always" Nathan Zimmer
2012-10-04 16:37 ` Joe Perches
2012-10-05 13:55 ` Nathan Zimmer
2012-10-05 14:14 ` Joe Perches
2012-10-05 14:54 ` Nathan Zimmer
2012-10-05 15:16 ` Bjorn Helgaas
2012-10-05 15:27 ` Joe Perches
2012-10-05 15:47 ` Nathan Zimmer
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='CAErSpo7ZQEm9==nsGiH2c_ZG8LPP8MAA8M9xSPyWPtCW2EHUUQ@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nzimmer@sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).