linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ralph Campbell <rcampbell@nvidia.com>
To: Alistair Popple <apopple@nvidia.com>,
	linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Cc: dri-devel@lists.freedesktop.org,
	John Hubbard <jhubbard@nvidia.com>,
	Alex Sierra <alex.sierra@amd.com>,
	Ben Skeggs <bskeggs@redhat.com>,
	Felix Kuehling <Felix.Kuehling@amd.com>,
	Lyude Paul <lyude@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH] mm/migrate_device: Return number of migrating pages in args->cpages
Date: Mon, 14 Nov 2022 15:58:41 -0800	[thread overview]
Message-ID: <1284e397-6d33-af04-ced6-7cc5f8628847@nvidia.com> (raw)
In-Reply-To: <20221111005135.1344004-1-apopple@nvidia.com>


On 11/10/22 16:51, Alistair Popple wrote:
> migrate_vma->cpages originally contained a count of the number of
> pages migrating including non-present pages which can be poluated

"populated"

> directly on the target.
>
> Commit 241f68859656 ("mm/migrate_device.c: refactor migrate_vma and
> migrate_deivce_coherent_page()") inadvertantly changed this to contain
> just the number of pages that were unmapped. Usage of
> migrate_vma->cpages isn't documented, but most drivers use it to see
> if all the requested addresses can be migrated so restore the original
> behaviour.
>
> Fixes: 241f68859656 ("mm/migrate_device.c: refactor migrate_vma and migrate_deivce_coherent_page()")
> Signed-off-by: Alistair Popple <apopple@nvidia.com>
> Reported-by: Ralph Campbell <rcampbell@nvidia.com>

You can add
Reviewed-by: Ralph Campbell <rcampbell@nvidia.com>

Thanks!




  reply	other threads:[~2022-11-14 23:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  0:51 Alistair Popple
2022-11-14 23:58 ` Ralph Campbell [this message]
2022-11-16 11:59   ` Alistair Popple

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=1284e397-6d33-af04-ced6-7cc5f8628847@nvidia.com \
    --to=rcampbell@nvidia.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.sierra@amd.com \
    --cc=apopple@nvidia.com \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jgg@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-mm@kvack.org \
    --cc=lyude@redhat.com \
    --cc=mpe@ellerman.id.au \
    /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