[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241023182217.147ee87197b53d47057a4c06@linux-foundation.org>
Date: Wed, 23 Oct 2024 18:22:17 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Matthew Brost <matthew.brost@...el.com>
Cc: intel-xe@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org, simona.vetter@...ll.ch,
felix.kuehling@....com, apopple@...dia.com
Subject: Re: [PATCH v3 1/1] mm/migrate: Add migrate_device_pfns
On Wed, 23 Oct 2024 16:39:43 -0700 Matthew Brost <matthew.brost@...el.com> wrote:
> Part of series [1]. Sending as individual patch ahead of that series as
> this is a prerequisite for merging.
That's news to me - singleton patches are perfectly OK?
On Wed, 23 Oct 2024 16:39:44 -0700 Matthew Brost <matthew.brost@...el.com> wrote:
> Implement migrate_device_pfns to prepare an array of PFNs for migration.
> Handles non-contiguous ranges of device pages that require migration.
OK, that's "what". We're more interested in "why".
> +EXPORT_SYMBOL(migrate_device_pfns);
And it's exported to modules, which adds to the significance.
Please fully describe the reasons for proposing this change.
Powered by blists - more mailing lists