From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] x86/PCI: limit the size of the 64bit BAR to 256GB
Date: Sun, 10 Dec 2017 11:03:37 +0100 [thread overview]
Message-ID: <be4fe1d8-0e86-1c06-a489-e0beca65ea10@gmail.com> (raw)
In-Reply-To: <20171208175635.GB12367@bhelgaas-glaptop.roam.corp.google.com>
Am 08.12.2017 um 18:56 schrieb Bjorn Helgaas:
> On Wed, Dec 06, 2017 at 01:51:18PM -0600, Bjorn Helgaas wrote:
>> On Wed, Nov 29, 2017 at 03:12:29PM +0100, Christian König wrote:
>>> This avoids problems with Xen which hides some memory resources from the
>>> OS and potentially also allows memory hotplug while this fixup is
>>> enabled.
>> The patch itself is OK, but the changelog doesn't say enough about
>> what the problem is. I have no clue about what the Xen issue is or
>> why limiting the BAR to 256GB avoids the problem or what this has to
>> do with memory hotplug.
>>
>> For example, we should be able to tell why 256GB is the right number.
>> Maybe there's something specific in Xen you can reference? Maybe an
>> example of what goes wrong with some details?
> Ping?
Sorry for the delay, first been to busy and then got a bad cold and
today is the first day I've got out of bed again.
> Is this change required to fix issues people are seeing? If
> so, we either need to rework the changelog and get it merged, or
> revert the quirk as a whole.
It's just a precaution to eventually avoid problems, I will try to
provided a patch with updated commit log tomorrow.
> I tentatively applied the first two patches to for-linus, but I
> haven't asked Linus to pull them because I assumed we really needed
> all three.
The first two patches are perfectly enough for now.
Thanks,
Christian.
>
> Bjorn
>
>>> 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-12-10 10:03 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 ` [PATCH 3/3] x86/PCI: limit the size of the 64bit BAR to 256GB Christian König
2017-12-06 19:51 ` Bjorn Helgaas
2017-12-08 17:56 ` Bjorn Helgaas
2017-12-08 21:30 ` Boris Ostrovsky
2017-12-10 10:03 ` Christian König [this message]
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=be4fe1d8-0e86-1c06-a489-e0beca65ea10@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=christian.koenig@amd.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
Powered by JetHome