On Tue, Oct 2, 2012 at 8:23 AM, Nathan Zimmer <nzimmer@xxxxxxx> 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@xxxxxxxxxx> > Cc: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> > > Signed-off-by: Nathan Zimmer <nzimmer@xxxxxxx> > --- > 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 > -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
