[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6434ba24-a219-6a5a-d902-0b48974a0e43@amd.com>
Date: Thu, 27 Jan 2022 17:20:40 -0600
From: "Sierra Guiza, Alejandro (Alex)" <alex.sierra@....com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Felix.Kuehling@....com, linux-mm@...ck.org, rcampbell@...dia.com,
linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org,
amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
hch@....de, jgg@...dia.com, jglisse@...hat.com, apopple@...dia.com,
willy@...radead.org,
"Deucher, Alexander" <Alexander.Deucher@....com>
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.
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@....com> 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?
>
Powered by blists - more mailing lists