[PATCH v4 00/10] Add MEMORY_DEVICE_COHERENT for coherent device memory mapping
Alexander.Deucher at amd.com
Fri Jan 28 15:00:54 UTC 2022
> -----Original Message-----
> From: Sierra Guiza, Alejandro (Alex) <Alex.Sierra at amd.com>
> Sent: Thursday, January 27, 2022 6:21 PM
> To: Andrew Morton <akpm at linux-foundation.org>
> Cc: Kuehling, Felix <Felix.Kuehling at amd.com>; linux-mm at kvack.org;
> rcampbell at nvidia.com; linux-ext4 at vger.kernel.org; linux-
> xfs at vger.kernel.org; amd-gfx at lists.freedesktop.org; dri-
> devel at lists.freedesktop.org; hch at lst.de; jgg at nvidia.com;
> jglisse at redhat.com; apopple at nvidia.com; willy at infradead.org; Deucher,
> Alexander <Alexander.Deucher at amd.com>
> Subject: Re: [PATCH v4 00/10] Add MEMORY_DEVICE_COHERENT for
> coherent device memory mapping
> We're somehow new on this procedure. Are you referring to rebase this
> patch series to git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
> <5.17-rc1 tag>?
> Alex Sierra
> Alex Deucher,
> Just a quick heads up. This patch series contains changes to the amdgpu
> driver which we're planning to merge through Andrew's tree, If that's ok with
> Alex Sierra
> On 1/27/2022 4:32 PM, Andrew Morton wrote:
> > On Wed, 26 Jan 2022 21:09:39 -0600 Alex Sierra <alex.sierra at amd.com>
> >> This patch series introduces MEMORY_DEVICE_COHERENT, a type of
> >> owned by a device that can be mapped into CPU page tables like
> >> MEMORY_DEVICE_GENERIC and can also be migrated like
> >> MEMORY_DEVICE_PRIVATE.
> > Some more reviewer input appears to be desirable here.
> > I was going to tentatively add it to -mm and -next, but problems.
> > 5.17-rc1's mm/migrate.c:migrate_vma_check_page() is rather different
> > from the tree you patched. Please redo, refresh and resend?
More information about the amd-gfx