[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220127143258.8da663659948ad1e6f0c0ea8@linux-foundation.org>
Date: Thu, 27 Jan 2022 14:32:58 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Alex Sierra <alex.sierra@....com>
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>
Subject: Re: [PATCH v4 00/10] Add MEMORY_DEVICE_COHERENT for coherent device
memory mapping
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