[PATCH 1/5] drm: Remove PageReserved manipulation from drm_pci_alloc
Chris Wilson
chris at chris-wilson.co.uk
Tue Feb 4 22:59:41 UTC 2020
Quoting Alex Deucher (2020-02-03 21:49:48)
> On Sun, Feb 2, 2020 at 12:16 PM Chris Wilson <chris at chris-wilson.co.uk> wrote:
> >
> > drm_pci_alloc/drm_pci_free are very thin wrappers around the core dma
> > facilities, and we have no special reason within the drm layer to behave
> > differently. In particular, since
> >
> > commit de09d31dd38a50fdce106c15abd68432eebbd014
> > Author: Kirill A. Shutemov <kirill.shutemov at linux.intel.com>
> > Date: Fri Jan 15 16:51:42 2016 -0800
> >
> > page-flags: define PG_reserved behavior on compound pages
> >
> > As far as I can see there's no users of PG_reserved on compound pages.
> > Let's use PF_NO_COMPOUND here.
> >
> > it has been illegal to combine GFP_COMP with SetPageReserved, so lets
> > stop doing both and leave the dma layer to its own devices.
> >
> > Reported-by: Taketo Kabe
>
> Needs an email address.
None provided, I don't insist that they opt in to potential spam
harvesting.
> > Closes: https://gitlab.freedesktop.org/drm/intel/issues/1027
>
> Should be Bug: rather than Closes:
We're using Closes for gitlab, since we hope to integrate with gitlab
someday. (Or at least some integrated bug/source management, of which
gitlab is the current forerunner.)
-Chris
More information about the dri-devel
mailing list