linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Jane Chu <jane.chu@oracle.com>, <akpm@linux-foundation.org>,
	<linux-mm@kvack.org>
Cc: Tony Luck <tony.luck@intel.com>,
	Miaohe Lin <linmiaohe@huawei.com>, <nao.horiguchi@gmail.com>,
	Matthew Wilcox <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>,
	Muchun Song <muchun.song@linux.dev>,
	Benjamin LaHaise <bcrl@kvack.org>, <jglisse@redhat.com>,
	Zi Yan <ziy@nvidia.com>, Jiaqi Yan <jiaqiyan@google.com>,
	Hugh Dickins <hughd@google.com>,
	Vishal Moola <vishal.moola@gmail.com>,
	Alistair Popple <apopple@nvidia.com>,
	Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH v3 3/5] mm: migrate: support poisoned recover from migrate folio
Date: Wed, 29 May 2024 10:19:23 +0800	[thread overview]
Message-ID: <da21a54d-823d-4767-9299-0cb668243708@huawei.com> (raw)
In-Reply-To: <9f0fbc29-b61a-40cb-94e1-eb40e6542e59@oracle.com>



On 2024/5/29 4:15, Jane Chu wrote:
>> +
>> +    if (unlikely(folio_mc_copy(dst, src))) {
>> +        if (mapping)
>> +            folio_ref_unfreeze(src, expected_cnt);
>> +        return -EFAULT;
>> +    }
> 
> Why not return what folio_mc_copy() returns?

The old version has ret of folio_mc_copy(),  but omit it in this
version, no strong option, I could add it back, thanks.

> 
> Similar comment for patch 4/5 as well.
> 
> -jane
> 
>> +
>> +    __folio_migrate_mapping(mapping, dst, src, expected_cnt);
>>       if (src_private)
>>           folio_attach_private(dst, folio_detach_private(src));
>> -    folio_migrate_copy(dst, src);
>> +    folio_migrate_flags(dst, src);
>>       return MIGRATEPAGE_SUCCESS;
>>   }


  reply	other threads:[~2024-05-29  2:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 13:45 [PATCH v3 0/5] mm: migrate: support poison " Kefeng Wang
2024-05-28 13:45 ` [PATCH v3 1/5] mm: add folio_mc_copy() Kefeng Wang
2024-05-28 14:17   ` Lance Yang
2024-05-29  2:16     ` Kefeng Wang
2024-05-28 20:13   ` Jane Chu
2024-05-29  2:16     ` Kefeng Wang
2024-05-28 13:45 ` [PATCH v3 2/5] mm: migrate: split folio_migrate_mapping() Kefeng Wang
2024-05-28 13:45 ` [PATCH v3 3/5] mm: migrate: support poisoned recover from migrate folio Kefeng Wang
2024-05-28 20:15   ` Jane Chu
2024-05-29  2:19     ` Kefeng Wang [this message]
2024-05-28 13:45 ` [PATCH v3 4/5] fs: hugetlbfs: support poison recover from hugetlbfs_migrate_folio() Kefeng Wang
2024-05-28 15:41   ` Luck, Tony
2024-05-28 20:19     ` Jane Chu
2024-05-28 20:30       ` Luck, Tony
2024-05-28 22:02         ` Jane Chu
2024-05-28 22:10           ` Luck, Tony
2024-05-29  2:48     ` Kefeng Wang
2024-05-28 13:45 ` [PATCH v3 5/5] mm: migrate: remove folio_migrate_copy() Kefeng Wang

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=da21a54d-823d-4767-9299-0cb668243708@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=bcrl@kvack.org \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=jane.chu@oracle.com \
    --cc=jglisse@redhat.com \
    --cc=jiaqiyan@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    --cc=tony.luck@intel.com \
    --cc=vishal.moola@gmail.com \
    --cc=willy@infradead.org \
    --cc=ziy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox