From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: [PATCH v2 02/10] PCI, x86: clip firmware assigned resource under parent bridge's
Date: Wed, 14 Jan 2015 20:31:29 -0800 [thread overview]
Message-ID: <1421296297-6371-3-git-send-email-yinghai@kernel.org> (raw)
In-Reply-To: <1421296297-6371-1-git-send-email-yinghai@kernel.org>
Some bios put range that is not fully coverred by root bus resources.
Try to clip them and update them in pci bridge bars.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=85491
Reported-by: Marek Kordik <kordikmarek@gmail.com>
Tested-by: Marek Kordik <kordikmarek@gmail.com>
Fixes: 5b28541552ef ("PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources")
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org
---
arch/x86/pci/i386.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/pci/i386.c b/arch/x86/pci/i386.c
index 9b18ef3..349c0d3 100644
--- a/arch/x86/pci/i386.c
+++ b/arch/x86/pci/i386.c
@@ -216,7 +216,7 @@ static void pcibios_allocate_bridge_resources(struct pci_dev *dev)
continue;
if (r->parent) /* Already allocated */
continue;
- if (!r->start || pci_claim_resource(dev, idx) < 0) {
+ if (!r->start || pci_claim_bridge_resource(dev, idx) < 0) {
/*
* Something is wrong with the region.
* Invalidate the resource to prevent
--
1.8.4.5
next prev parent reply other threads:[~2015-01-15 4:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 4:31 [PATCH v2 00/10] PCI: clip firmware assigned resources Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 01/10] PCI: clip firmware assigned resource under parent bridge's Yinghai Lu
2015-01-15 4:31 ` Yinghai Lu [this message]
2015-01-15 4:31 ` [PATCH v2 03/10] PCI, alpha: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 04/10] PCI, frv: " Yinghai Lu
2015-01-15 4:51 ` Yinghai Lu
2015-01-15 16:19 ` Bjorn Helgaas
2015-01-15 4:31 ` [PATCH v2 05/10] PCI, ia64: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 06/10] PCI, microblaze: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 07/10] PCI, mn10300: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 08/10] PCI, parisc: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 09/10] PCI, powerpc: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 10/10] PCI, sparc: " Yinghai Lu
2015-01-16 0:14 ` David Miller
2015-01-15 22:24 ` [PATCH v2 00/10] PCI: clip firmware assigned resources Bjorn Helgaas
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=1421296297-6371-3-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).