All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Popple <apopple@nvidia.com>
To: Ralph Campbell <rcampbell@nvidia.com>
Cc: Alex Sierra <alex.sierra@amd.com>,
	John Hubbard <jhubbard@nvidia.com>,
	Felix Kuehling <Felix.Kuehling@amd.com>,
	dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
	Ben Skeggs <bskeggs@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm/migrate_device: Return number of migrating pages in args->cpages
Date: Wed, 16 Nov 2022 22:59:51 +1100	[thread overview]
Message-ID: <87fsejumdr.fsf@nvidia.com> (raw)
In-Reply-To: <1284e397-6d33-af04-ced6-7cc5f8628847@nvidia.com>


Hi Andrew,

I realize it's getting late in the cycle but any chance you could take
this one as well for v6.1-rc6? It fixes a minor bug introduced in
v6.1-rc1 which could cause some drivers to think they can't migrate
pages when they can. Thanks.

Ralph Campbell <rcampbell@nvidia.com> writes:

> 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!


WARNING: multiple messages have this Message-ID (diff)
From: Alistair Popple <apopple@nvidia.com>
To: Ralph Campbell <rcampbell@nvidia.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	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: Wed, 16 Nov 2022 22:59:51 +1100	[thread overview]
Message-ID: <87fsejumdr.fsf@nvidia.com> (raw)
In-Reply-To: <1284e397-6d33-af04-ced6-7cc5f8628847@nvidia.com>


Hi Andrew,

I realize it's getting late in the cycle but any chance you could take
this one as well for v6.1-rc6? It fixes a minor bug introduced in
v6.1-rc1 which could cause some drivers to think they can't migrate
pages when they can. Thanks.

Ralph Campbell <rcampbell@nvidia.com> writes:

> 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-16 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  0:51 [PATCH] mm/migrate_device: Return number of migrating pages in args->cpages Alistair Popple
2022-11-11  0:51 ` Alistair Popple
2022-11-14 23:58 ` Ralph Campbell
2022-11-14 23:58   ` Ralph Campbell
2022-11-16 11:59   ` Alistair Popple [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=87fsejumdr.fsf@nvidia.com \
    --to=apopple@nvidia.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.sierra@amd.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=mpe@ellerman.id.au \
    --cc=rcampbell@nvidia.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.