linux-kernel - [PATCH] quiet MMCONFIG related printks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200701012101.38427.jbarnes@virtuousgeek.org>
Date:	Mon, 1 Jan 2007 21:01:38 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>
Cc:	Arjan van de Ven <arjan@...radead.org>
Subject: [PATCH] quiet MMCONFIG related printks

Using MMCONFIG for PCI config space access is simply an optimization, not
a requirement.  Therefore, when it can't be used, there's no need for
KERN_ERR level message.  This patch makes the message a KERN_INFO instead
to reduce some of the noise in a kernel boot with the 'quiet' option.
(Note that this has no effect on a normal boot, which is ridiculously
verbose these days.)

Signed-off-by:  Jesse Barnes <jbarnes@...tuousgeek.org>

Thanks,
Jesse

diff --git a/arch/i386/pci/mmconfig.c b/arch/i386/pci/mmconfig.c
index e2616a2..b95e7f3 100644
--- a/arch/i386/pci/mmconfig.c
+++ b/arch/i386/pci/mmconfig.c
@@ -210,9 +210,9 @@ void __init pci_mmcfg_init(int type)
 	if (type == 1 && !e820_all_mapped(pci_mmcfg_config[0].base_address,
 			pci_mmcfg_config[0].base_address + MMCONFIG_APER_MIN,
 			E820_RESERVED)) {
-		printk(KERN_ERR "PCI: BIOS Bug: MCFG area at %x is not E820-reserved\n",
+		printk(KERN_INFO "PCI: BIOS Bug: MCFG area at %x is not E820-reserved\n",
 				pci_mmcfg_config[0].base_address);
-		printk(KERN_ERR "PCI: Not using MMCONFIG.\n");
+		printk(KERN_INFO "PCI: Not using MMCONFIG.\n");
 		return;
 	}
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/