public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <mawilcox@linuxonhyperv.com>
To: x86@kernel.org, linux-kernel@vger.kernel.org, linux-nvdimm@ml01.01.org
Cc: Matthew Wilcox <mawilcox@microsoft.com>
Subject: [PATCH 2/2] x86: Turn down the scary 'no PCI' warning
Date: Thu, 18 Aug 2016 12:12:55 -0700	[thread overview]
Message-ID: <1471547575-14748-2-git-send-email-mawilcox@linuxonhyperv.com> (raw)
In-Reply-To: <1471547575-14748-1-git-send-email-mawilcox@linuxonhyperv.com>

From: Matthew Wilcox <mawilcox@microsoft.com>

Hyper-V Generation 2 guests do not have PCI hardware.  It is therefore not
'Fatal' to lack PCI config space, and those booting with the 'quiet' option
do not need to see a message at all.  I deem this to be 'informational'
rather than 'normal but significant', at least on some hardware.

Signed-off-by: Matthew Wilcox <mawilcox@microsoft.com>
---
 arch/x86/pci/init.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/arch/x86/pci/init.c b/arch/x86/pci/init.c
index adb62aa..595840a 100644
--- a/arch/x86/pci/init.c
+++ b/arch/x86/pci/init.c
@@ -32,8 +32,7 @@ static __init int pci_arch_init(void)
 	pci_direct_init(type);
 #endif
 	if (!raw_pci_ops && !raw_pci_ext_ops)
-		printk(KERN_ERR
-		"PCI: Fatal: No config space access function found\n");
+		pr_info("PCI: No config space access function found\n");
 
 	dmi_check_pciprobe();
 
-- 
2.8.1

  parent reply	other threads:[~2016-08-19  1:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 19:12 [PATCH 1/2] x86: Set up resources correctly on Hyper-V Generation 2 Matthew Wilcox
2016-08-18 17:31 ` Dan Williams
2016-08-18 17:50   ` Matthew Wilcox
2016-08-18 18:02     ` Dan Williams
2016-08-18 18:05       ` Matthew Wilcox
2016-08-18 18:15         ` Dan Williams
2016-08-18 18:26           ` Matthew Wilcox
2016-08-18 19:12             ` Dan Williams
2016-08-18 19:56               ` Matthew Wilcox
2016-08-18 20:16                 ` Dan Williams
2016-08-18 21:26                   ` Matthew Wilcox
2016-08-18 19:12 ` Matthew Wilcox [this message]
2016-08-19 16:06 ` Konrad Rzeszutek Wilk
2016-08-19 16:46   ` Matthew Wilcox

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=1471547575-14748-2-git-send-email-mawilcox@linuxonhyperv.com \
    --to=mawilcox@linuxonhyperv.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=mawilcox@microsoft.com \
    --cc=x86@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