From: "Christian König" <deathsimple@vodafone.de>
To: linux-pci@vger.kernel.org, platform-driver-x86@vger.kernel.org,
helgaas@kernel.org
Subject: Resizeable PCI BAR support v6
Date: Tue, 9 May 2017 18:49:02 +0200 [thread overview]
Message-ID: <1494348547-1465-1-git-send-email-deathsimple@vodafone.de> (raw)
Hi everyone,
is is the sixth incarnation of this set of patches. It enables device
drivers to resize and most likely also relocate the PCI BAR of devices
they manage to allow the CPU to access all of the device local memory at once.
This is very useful for GFX device drivers where the default PCI BAR is only
about 256MB in size for compatibility reasons, but the device easily have
multiple gigabyte of local memory.
Noteable changed compared to v5:
1. Added some rb.
2. Followed Andy's suggestion on patch #3 to use a next
pointer to make it more readable.
Mostly every comment addressed now, so next question is how we want to
merge this upstream?
I would suggest patches #1-#4 through some PCI branch and we send #5 through the drm
maintainer as soon as the dependencies are accepted?
Thanks for all the help,
Christian.
next reply other threads:[~2017-05-09 16:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 16:49 Christian König [this message]
2017-05-09 16:49 ` [PATCH v6 1/5] PCI: add a define for the PCI resource type mask v2 Christian König
2017-05-09 16:49 ` [PATCH v6 2/5] PCI: add resizeable BAR infrastructure v5 Christian König
2017-05-09 16:49 ` [PATCH v6 3/5] PCI: add functionality for resizing resources v5 Christian König
2017-05-11 11:56 ` Andy Shevchenko
2017-05-11 11:56 ` Andy Shevchenko
2017-05-09 16:49 ` [PATCH v6 4/5] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors v3 Christian König
2017-05-09 16:49 ` [PATCH v6 5/5] drm/amdgpu: resize VRAM BAR for CPU access v2 Christian König
2017-05-11 12:00 ` Andy Shevchenko
2017-05-11 12:00 ` Andy Shevchenko
2017-06-01 20:14 ` Bjorn Helgaas
2017-06-01 20:14 ` Bjorn Helgaas
2017-06-02 9:32 ` Christian König
2017-06-02 20:26 ` Bjorn Helgaas
[not found] ` <20170602202631.GA1452-1RhO1Y9PlrlHTL0Zs8A6p5iNqAH0jzoTYJqu5kTmcBRl57MIdRCFDg@public.gmane.org>
2017-06-06 11:51 ` Christian König
2017-06-06 11:51 ` Christian König
[not found] ` <779a883a-265a-ae04-b0cd-8cb3599f0dc0-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-06-06 13:53 ` Alex Deucher
2017-06-06 13:53 ` Alex Deucher
2017-06-06 23:10 ` Bjorn Helgaas
2017-06-07 3:50 ` Deucher, Alexander
2017-06-07 3:50 ` Deucher, Alexander
[not found] ` <20170606231019.GC12672-1RhO1Y9PlrlHTL0Zs8A6p5iNqAH0jzoTYJqu5kTmcBRl57MIdRCFDg@public.gmane.org>
2017-06-09 8:59 ` Christian König
2017-06-09 8:59 ` Christian König
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=1494348547-1465-1-git-send-email-deathsimple@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=helgaas@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.