All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Christian König" <deathsimple@vodafone.de>
Cc: linux-pci@vger.kernel.org, dri-devel@lists.freedesktop.org,
	platform-driver-x86@vger.kernel.org,
	amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors
Date: Wed, 17 May 2017 16:36:45 -0500	[thread overview]
Message-ID: <20170517213645.GA21886@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <de846814-5884-69a5-3eb6-fec5c5c6896d@vodafone.de>

On Tue, Apr 25, 2017 at 03:01:35PM +0200, Christian König wrote:
> Am 12.04.2017 um 18:55 schrieb Bjorn Helgaas:
> >[SNIP]
> >>>I think the specs would envision this being done via an ACPI _SRS
> >>>method on the PNP0A03 host bridge device.  That would be a more
> >>>generic path that would work on any host bridge.  Did you explore that
> >>>possibility?  I would prefer to avoid adding device-specific code if
> >>>that's possible.
> >>I've checked quite a few boards, but none of them actually
> >>implements it this way.
> >>
> >>M$ is working on a new ACPI table to enable this vendor neutral, but
> >>I guess that will still take a while.
> >>
> >>I want to support this for all AMD CPU released in the past 5 years
> >>or so, so we are going to deal with a bunch of older boards as well.
> >I've never seen _SRS for host bridges either.  I'm curious about what
> >sort of new table will be proposed.  It seems like the existing ACPI
> >resource framework could manage it, but I certainly don't know all the
> >issues.
> 
> No idea either since I'm not involved into that. My job is to get it
> working on the existing hw generations and that alone is enough work
> :)
> 
> My best guess is that MS is going to either make _SRS on the host
> bridge or a pre-configured 64bit window mandatory for the BIOS.

While researching something else, I noticed that the PCI Firmware Spec, rev
3.2, does indeed call out _PRS and _SRS as the mechanism for the OS to
configure host bridge windows.  See sections 4.1.3, 4.3.2.1, and 4.6.5.

Sec 4.6.5 also includes an implementation note that might be a clue about
the "compatibility issues" that prevent the BIOS from enabling the window
in the first place.

I'd like to incorporate some of this info into these changes, probably in a
code comment and changelog, so we can encourage a more generic approach in
the future, even if we can't use it in all existing cases.

Bjorn

  reply	other threads:[~2017-05-17 21:37 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 12:41 Resizeable PCI BAR support V3 Christian König
2017-03-13 12:41 ` Christian König
2017-03-13 12:41 ` [PATCH 1/4] PCI: add resizeable BAR infrastructure v3 Christian König
2017-03-13 12:41   ` Christian König
2017-03-14 13:09   ` kbuild test robot
2017-03-14 13:09     ` kbuild test robot
2017-03-24 15:28   ` Bjorn Helgaas
2017-03-13 12:41 ` [PATCH 2/4] PCI: add functionality for resizing resources v2 Christian König
2017-03-13 12:41   ` Christian König
2017-03-13 16:43   ` Andy Shevchenko
2017-03-13 16:43     ` Andy Shevchenko
2017-03-13 16:43     ` Andy Shevchenko
2017-04-11  9:14     ` Christian König
2017-04-11  9:14       ` Christian König
2017-03-14  9:01   ` kbuild test robot
2017-03-24 21:34   ` Bjorn Helgaas
2017-04-11 15:37     ` Christian König
2017-04-12 16:37       ` Bjorn Helgaas
2017-03-13 12:41 ` [PATCH 3/4] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors Christian König
2017-03-13 12:41   ` Christian König
2017-03-13 16:49   ` Andy Shevchenko
2017-03-13 16:49     ` Andy Shevchenko
2017-03-13 16:49     ` Andy Shevchenko
2017-04-11  9:21     ` Christian König
2017-04-11  9:21       ` Christian König
2017-03-14  9:25   ` kbuild test robot
2017-03-14  9:25     ` kbuild test robot
2017-03-24 15:47   ` Bjorn Helgaas
2017-03-24 15:47     ` Bjorn Helgaas
2017-04-11 15:48     ` Christian König
2017-04-11 15:48       ` Christian König
2017-04-12 16:55       ` Bjorn Helgaas
2017-04-25 13:01         ` Christian König
2017-05-17 21:36           ` Bjorn Helgaas [this message]
2017-03-13 12:41 ` [PATCH 4/4] drm/amdgpu: resize VRAM BAR for CPU access Christian König
2017-03-13 12:41   ` Christian König
2017-03-13 16:51   ` Andy Shevchenko
2017-03-13 16:51     ` Andy Shevchenko
2017-03-15  7:23   ` Ayyappa Ch
2017-03-15  7:23     ` Ayyappa Ch
2017-03-15  7:23     ` Ayyappa Ch
2017-03-15  7:37     ` Christian König
2017-03-15  7:37       ` Christian König
2017-03-15  8:25       ` Zhou, David(ChunMing)
2017-03-15  8:25         ` Zhou, David(ChunMing)
2017-03-15  8:25         ` Zhou, David(ChunMing)
2017-03-15  9:29         ` Christian König
2017-03-15  9:29           ` Christian König
2017-03-15  9:29           ` Christian König
2017-03-16  2:19           ` Zhang, Jerry
2017-03-16  2:19             ` Zhang, Jerry
2017-03-16  2:19             ` Zhang, Jerry
2017-03-16  2:25             ` Alex Deucher
2017-03-16  2:25               ` Alex Deucher
2017-03-16  2:25               ` Alex Deucher
2017-03-16  2:41               ` Zhang, Jerry
2017-03-16  2:41                 ` Zhang, Jerry
2017-03-23 14:30                 ` Sagalovitch, Serguei
2017-03-23 14:30                   ` Sagalovitch, Serguei
2017-03-23 14:30                   ` Sagalovitch, Serguei
2017-03-23 15:56                   ` Christian König
2017-03-23 15:56                     ` Christian König
2017-03-15 10:42       ` Ayyappa Ch
2017-03-15 10:42         ` Ayyappa Ch
2017-03-15 10:42         ` Ayyappa Ch
2017-03-15 11:03         ` Christian König
2017-03-15 11:03           ` Christian König
2017-03-15 16:08       ` Deucher, Alexander
2017-03-15 16:08         ` Deucher, Alexander
2017-03-15 16:08         ` Deucher, Alexander
2017-03-24 21:42   ` Bjorn Helgaas
2023-03-10 14:05 [PATCH 3/4] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors Brandi Gulbin

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=20170517213645.GA21886@bhelgaas-glaptop.roam.corp.google.com \
    --to=helgaas@kernel.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.