From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: helgaas@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] x86/PCI: limit the size of the 64bit BAR to 256GB
Date: Wed, 29 Nov 2017 15:12:29 +0100 [thread overview]
Message-ID: <20171129141229.6107-4-christian.koenig@amd.com> (raw)
In-Reply-To: <20171129141229.6107-1-christian.koenig@amd.com>
This avoids problems with Xen which hides some memory resources from the
OS and potentially also allows memory hotplug while this fixup is
enabled.
Signed-off-by: Christian König <christian.koenig@amd.com>
---
arch/x86/pci/fixup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
index c817ab85dc82..149adbc7f2a3 100644
--- a/arch/x86/pci/fixup.c
+++ b/arch/x86/pci/fixup.c
@@ -701,7 +701,7 @@ static void pci_amd_enable_64bit_bar(struct pci_dev *dev)
res->name = "PCI Bus 0000:00";
res->flags = IORESOURCE_PREFETCH | IORESOURCE_MEM |
IORESOURCE_MEM_64 | IORESOURCE_WINDOW;
- res->start = 0x100000000ull;
+ res->start = 0xbd00000000ull;
res->end = 0xfd00000000ull - 1;
/* Just grab the free area behind system memory for this */
--
2.11.0
next prev parent reply other threads:[~2017-11-29 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 14:12 Fixes for 64bit window handling on AMD CPUs Christian König
2017-11-29 14:12 ` [PATCH 1/3] x86/PCI: fix infinity loop in search for 64bit BAR placement Christian König
2017-11-29 14:12 ` [PATCH 2/3] x86/PCI: only enable a 64bit BAR on single socket AMD Family 15h systems Christian König
2017-11-29 14:12 ` Christian König [this message]
2017-12-06 19:51 ` [PATCH 3/3] x86/PCI: limit the size of the 64bit BAR to 256GB Bjorn Helgaas
2017-12-08 17:56 ` Bjorn Helgaas
2017-12-08 21:30 ` Boris Ostrovsky
2017-12-10 10:03 ` Christian König
2017-12-06 20:51 ` Fixes for 64bit window handling on AMD CPUs 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=20171129141229.6107-4-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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
all inboxes | Powered by JetHome®