mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	simona.vetter@ffwll.ch, felix.kuehling@amd.com,
	apopple@nvidia.com
Subject: Re: [PATCH v3 1/1] mm/migrate: Add migrate_device_pfns
Date: Wed, 23 Oct 2024 18:22:17 -0700	[thread overview]
Message-ID: <20241023182217.147ee87197b53d47057a4c06@linux-foundation.org> (raw)
In-Reply-To: <20241023233944.1798835-2-matthew.brost@intel.com>

On Wed, 23 Oct 2024 16:39:43 -0700 Matthew Brost <matthew.brost@intel.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@intel.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.

  reply	other threads:[~2024-10-24  1:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 23:39 [PATCH v3 0/1] " Matthew Brost
2024-10-23 23:39 ` [PATCH v3 1/1] " Matthew Brost
2024-10-24  1:22   ` Andrew Morton [this message]
2024-10-24  1:50     ` Matthew Brost
2024-10-24  2:22       ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241023182217.147ee87197b53d47057a4c06@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felix.kuehling@amd.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew.brost@intel.com \
    --cc=simona.vetter@ffwll.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®