linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: David Hildenbrand <david@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Oscar Salvador <osalvador@suse.de>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Naoya Horiguchi <nao.horiguchi@gmail.com>, <linux-mm@kvack.org>
Subject: Re: [PATCH 1/4] mm: memory-failure: add unmap_posioned_folio()
Date: Wed, 31 Jul 2024 12:46:03 +0800	[thread overview]
Message-ID: <aed5f4a6-37d0-42eb-ae58-3067872dc66a@huawei.com> (raw)
In-Reply-To: <95d372e0-e272-4669-a3cc-7da32e866504@redhat.com>



On 2024/7/30 18:20, David Hildenbrand wrote:
> On 25.07.24 03:16, Kefeng Wang wrote:
>> Add unmap_posioned_folio() helper which will be reused by
>> do_migrate_range() from memory hotplug soon.
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>>   mm/internal.h       |  9 +++++++++
>>   mm/memory-failure.c | 43 ++++++++++++++++++++++++++-----------------
>>   2 files changed, 35 insertions(+), 17 deletions(-)
>>
>> diff --git a/mm/internal.h b/mm/internal.h
>> index 7a3bcc6d95e7..c5bd24c4fa3a 100644
>> --- a/mm/internal.h
>> +++ b/mm/internal.h
>> @@ -1069,6 +1069,8 @@ static inline int find_next_best_node(int node, 
>> nodemask_t *used_node_mask)
>>   /*
>>    * mm/memory-failure.c
>>    */
>> +#ifdef CONFIG_MEMORY_FAILURE
>> +int unmap_posioned_folio(struct folio *folio, enum ttu_flags ttu);
>>   void shake_folio(struct folio *folio);
>>   extern int hwpoison_filter(struct page *p);
>> @@ -1089,6 +1091,13 @@ void add_to_kill_ksm(struct task_struct *tsk, 
>> struct page *p,
>>                unsigned long ksm_addr);
>>   unsigned long page_mapped_in_vma(struct page *page, struct 
>> vm_area_struct *vma);
>> +#else
>> +static inline int unmap_posioned_folio(struct folio *folio, enum 
>> ttu_flags ttu)
>> +{
>> +    return 0;
>> +}
>> +#endif
>> +
> 
> Was wondering if we could come up with a better name (something that 
> starts with folio_*), but wasn't able to come up with something I liked 
> more.

Uh, pool at naming, I can't find a better one...
> 
> Acked-by: David Hildenbrand <david@redhat.com>
> 
Thanks.


  reply	other threads:[~2024-07-31  4:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  1:16 [PATCH 0/4] mm: memory_hotplug: improve do_migrate_range() Kefeng Wang
2024-07-25  1:16 ` [PATCH 1/4] mm: memory-failure: add unmap_posioned_folio() Kefeng Wang
2024-07-30 10:20   ` David Hildenbrand
2024-07-31  4:46     ` Kefeng Wang [this message]
2024-07-25  1:16 ` [PATCH 2/4] mm: memory_hotplug: check hwpoisoned page firstly in do_migrate_range() Kefeng Wang
2024-07-30 10:26   ` David Hildenbrand
2024-07-31  5:09     ` Kefeng Wang
2024-08-01 20:10       ` David Hildenbrand
2024-08-02  7:50         ` Kefeng Wang
2024-08-06  9:29           ` David Hildenbrand
     [not found]             ` <1e6cccc5-fedc-8df6-1deb-16ceb52a4094@huawei.com>
     [not found]               ` <1e14d86d-0d17-41da-9400-16c9c6f93f8f@redhat.com>
2024-08-09  2:02                 ` Miaohe Lin
2024-08-01 20:14   ` David Hildenbrand
2024-08-02  8:02     ` Kefeng Wang
2024-08-06  3:44       ` Kefeng Wang
2024-08-06  9:24         ` David Hildenbrand
2024-08-06  9:15       ` David Hildenbrand
2024-07-25  1:16 ` [PATCH 3/4] mm: migrate: add isolate_folio_to_list() Kefeng Wang
2024-07-26 14:21   ` kernel test robot
2024-07-27  7:56     ` Kefeng Wang
2024-07-30 10:30   ` David Hildenbrand
2024-07-25  1:16 ` [PATCH 4/4] mm: memory_hotplug: unify Huge/LRU/non-LRU movable folio isolation Kefeng Wang
2024-07-30 10:31   ` David Hildenbrand
2024-07-31  5:13     ` Kefeng Wang
2024-08-01 20:16       ` David Hildenbrand
2024-08-01 20:23   ` David Hildenbrand
2024-08-02  8:39     ` 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=aed5f4a6-37d0-42eb-ae58-3067872dc66a@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    /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