From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
"Longlong Xia" <xialonglong1@huawei.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"sunnanyong@huawei.com" <sunnanyong@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 1/2] mm: memory-failure: Refactor add_to_kill()
Date: Thu, 13 Apr 2023 17:26:28 +0800 [thread overview]
Message-ID: <2797d1c1-34cd-5dab-0db2-84a1bf493716@huawei.com> (raw)
In-Reply-To: <20230331054142.GA1435482@hori.linux.bs1.fc.nec.co.jp>
On 2023/3/31 13:41, HORIGUCHI NAOYA(堀口 直也) wrote:
> On Thu, Mar 30, 2023 at 03:45:00PM +0800, Longlong Xia wrote:
>> The page_address_in_vma() is used to find the user virtual address of page
>> in add_to_kill(), but it doesn't support ksm due to the ksm page->index
>> unusable, add an addr as parameter to add_to_kill(), let's the caller to
>> pass it, also rename the function to __add_to_kill(), and adding
>> add_to_kill_anon_file() for handling anonymous pages and file pages,
>> adding add_to_kill_fsdax() for handling fsdax pages.
>>
>> Signed-off-by: Longlong Xia <xialonglong1@huawei.com>
>> ---
>> mm/memory-failure.c | 29 +++++++++++++++++++++--------
>> 1 file changed, 21 insertions(+), 8 deletions(-)
>>
>> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
>> index a1ede7bdce95e..9ca058f659121 100644
>> --- a/mm/memory-failure.c
>> +++ b/mm/memory-failure.c
>> @@ -405,9 +405,9 @@ static unsigned long dev_pagemap_mapping_shift(struct vm_area_struct *vma,
>> * page->mapping are sufficient for mapping the page back to its
>> * corresponding user virtual address.
>> */
>> -static void add_to_kill(struct task_struct *tsk, struct page *p,
>> - pgoff_t fsdax_pgoff, struct vm_area_struct *vma,
>> - struct list_head *to_kill)
>> +static void __add_to_kill(struct task_struct *tsk, struct page *p,
>> + struct vm_area_struct *vma, struct list_head *to_kill,
>> + unsigned long addr, pgoff_t fsdax_pgoff)
>
> Hi, Longlong,
>
> The new argument addr seems to be used only from add_to_kill_ksm(),
> so you can name the argument as such (like ksm_addr), as we do
> for fsdax_pgoff (which is clear to be used only for fsdax)?
Another option, move page_address_in_vma() from __add_to_kill() into
add_to_kill_[anon_file/fsdax](), but use ksm_addr is fine with me,
Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>
> Thanks,
> Naoya Horiguchi
next prev parent reply other threads:[~2023-04-13 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 7:44 [PATCH 0/2] mm: ksm: support hwpoison for ksm page Longlong Xia
2023-03-30 7:45 ` [PATCH 1/2] mm: memory-failure: Refactor add_to_kill() Longlong Xia
2023-03-31 5:41 ` HORIGUCHI NAOYA(堀口 直也)
2023-04-04 10:36 ` xialonglong
2023-04-13 9:26 ` Kefeng Wang [this message]
2023-03-30 7:45 ` [PATCH 2/2] mm: ksm: Support hwpoison for ksm page Longlong Xia
2023-03-31 5:42 ` HORIGUCHI NAOYA(堀口 直也)
2023-04-04 10:42 ` xialonglong
2023-04-13 8:00 ` xialonglong
2023-04-13 9:13 ` HORIGUCHI NAOYA(堀口 直也)
2023-04-13 9:30 ` 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=2797d1c1-34cd-5dab-0db2-84a1bf493716@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=sunnanyong@huawei.com \
--cc=xialonglong1@huawei.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