From: Miaohe Lin <linmiaohe@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Alex Sierra <alex.sierra@amd.com>, Christoph Hellwig <hch@lst.de>,
Felix Kuehling <Felix.Kuehling@amd.com>,
Alistair Poppple <apopple@nvidia.com>
Subject: Re: [PATCH] mm/migrate: skip unsupported ZONE_DEVICE page in migrate_vma_collect_pmd()
Date: Wed, 1 Jun 2022 09:54:29 +0800 [thread overview]
Message-ID: <2fa970ac-78c5-93a1-9de9-4a450d727918@huawei.com> (raw)
In-Reply-To: <20220531110517.51b839799201e9e75684375a@linux-foundation.org>
On 2022/6/1 2:05, Andrew Morton wrote:
> On Tue, 31 May 2022 20:25:30 +0800 Miaohe Lin <linmiaohe@huawei.com> wrote:
>
>> For now we only support migrating to un-addressable device memory. Other
>> types of ZONE_DEVICE pages are not supported yet. So skip those pages in
>> MIGRATE_VMA_SELECT_SYSTEM case to save useless effort.
>>
>
> https://lkml.kernel.org/r/20220531155629.20057-4-alex.sierra@amd.com
> just made similar-but-different changes here. Please review those.
>
> Normally I'm merge your fixlet ahead of the larger changes and redo
> Alex's patchset. Because Alex's larger patchset might never get
> mainlined, so your fixlet would then get lost.
>
> But in this case, your fixlet doesn't seem important enough to be
> churning things around in that way?
Yes. Above similar-but-different changes look good to me. I'm fine to drop
this patch.
Thanks!
>
>> --- a/mm/migrate_device.c
>> +++ b/mm/migrate_device.c
>> @@ -157,6 +157,11 @@ static int migrate_vma_collect_pmd(pmd_t *pmdp,
>> goto next;
>> }
>> page = vm_normal_page(migrate->vma, addr, pte);
>> + /*
>> + * Other types of ZONE_DEVICE page are not supported.
>> + */
>> + if (page && is_zone_device_page(page))
>> + goto next;
>> mpfn = migrate_pfn(pfn) | MIGRATE_PFN_MIGRATE;
>> mpfn |= pte_write(pte) ? MIGRATE_PFN_WRITE : 0;
>> }
>
> .
>
prev parent reply other threads:[~2022-06-01 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 12:25 Miaohe Lin
2022-05-31 18:05 ` Andrew Morton
2022-06-01 1:54 ` Miaohe Lin [this message]
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=2fa970ac-78c5-93a1-9de9-4a450d727918@huawei.com \
--to=linmiaohe@huawei.com \
--cc=Felix.Kuehling@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alex.sierra@amd.com \
--cc=apopple@nvidia.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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