[Public] > -----Original Message----- > From: Sierra Guiza, Alejandro (Alex) <Alex.Sierra@xxxxxxx> > Sent: Thursday, January 27, 2022 6:21 PM > To: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > Cc: Kuehling, Felix <Felix.Kuehling@xxxxxxx>; linux-mm@xxxxxxxxx; > rcampbell@xxxxxxxxxx; linux-ext4@xxxxxxxxxxxxxxx; linux- > xfs@xxxxxxxxxxxxxxx; amd-gfx@xxxxxxxxxxxxxxxxxxxxx; dri- > devel@xxxxxxxxxxxxxxxxxxxxx; hch@xxxxxx; jgg@xxxxxxxxxx; > jglisse@xxxxxxxxxx; apopple@xxxxxxxxxx; willy@xxxxxxxxxxxxx; Deucher, > Alexander <Alexander.Deucher@xxxxxxx> > Subject: Re: [PATCH v4 00/10] Add MEMORY_DEVICE_COHERENT for > coherent device memory mapping > > Andrew, > 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- > next.git > <5.17-rc1 tag>? > > Regards, > 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 > you. No problem. Thanks! Alex > > Regards, > 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@xxxxxxx> > wrote: > > > >> This patch series introduces MEMORY_DEVICE_COHERENT, a type of > memory > >> 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? > >
