From: Randy Dunlap <rdunlap@infradead.org>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
SeongJae Park <sj@kernel.org>
Subject: Re: mmotm 2021-12-29-20-07 uploaded (mm/damon)
Date: Thu, 30 Dec 2021 09:32:35 -0800 [thread overview]
Message-ID: <3ad11107-30d8-ab75-961b-8142404c8c21@infradead.org> (raw)
In-Reply-To: <1aaf9c11-0d8e-b92d-5c92-46e50a6e8d4e@linux.alibaba.com>
On 12/29/21 22:33, Baolin Wang wrote:
> Hi,
>
> On 12/30/2021 2:27 PM, Randy Dunlap wrote:
>> Hi--
>>
>> On 12/29/21 20:07, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2021-12-29-20-07 has been uploaded to
>>>
>>> https://www.ozlabs.org/~akpm/mmotm/
>>>
>>> mmotm-readme.txt says
>>>
>>> README for mm-of-the-moment:
>>>
>>> https://www.ozlabs.org/~akpm/mmotm/
>>>
>>> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
>>> more than once a week.
>>>
>>> You will need quilt to apply these patches to the latest Linus release (5.x
>>> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
>>> https://ozlabs.org/~akpm/mmotm/series
>>>
>>> The file broken-out.tar.gz contains two datestamp files: .DATE and
>>> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
>>> followed by the base kernel version against which this patch series is to
>>> be applied.
>>
>>
>> On i386:
>>
>> ../mm/damon/vaddr.c: In function ‘damon_hugetlb_mkold’:
>> ../mm/damon/vaddr.c:402:17: warning: unused variable ‘h’ [-Wunused-variable]
>> struct hstate *h = hstate_vma(vma);
>
> Ah, thanks for report, I think below changes can fix the warning. And I'll send a new version to address this warning.
Yes, that works. Thanks.
Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
> diff --git a/mm/damon/vaddr.c b/mm/damon/vaddr.c
> index bcdc602..25bff8a 100644
> --- a/mm/damon/vaddr.c
> +++ b/mm/damon/vaddr.c
> @@ -397,7 +397,6 @@ static void damon_hugetlb_mkold(pte_t *pte, struct mm_struct *mm,
> struct vm_area_struct *vma, unsigned long addr)
> {
> bool referenced = false;
> - struct hstate *h = hstate_vma(vma);
> pte_t entry = huge_ptep_get(pte);
> struct page *page = pte_page(entry);
>
> @@ -414,7 +413,7 @@ static void damon_hugetlb_mkold(pte_t *pte, struct mm_struct *mm,
> }
>
> #ifdef CONFIG_MMU_NOTIFIER
> - if (mmu_notifier_clear_young(mm, addr, addr + huge_page_size(h)))
> + if (mmu_notifier_clear_young(mm, addr, addr + huge_page_size(hstate_vma(vma))))
> referenced = true;
> #endif /* CONFIG_MMU_NOTIFIER */
--
~Randy
next prev parent reply other threads:[~2021-12-30 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 4:07 mmotm 2021-12-29-20-07 uploaded akpm
2021-12-30 6:27 ` mmotm 2021-12-29-20-07 uploaded (mm/damon) Randy Dunlap
2021-12-30 6:33 ` Baolin Wang
2021-12-30 17:32 ` Randy Dunlap [this message]
2021-12-30 8:42 ` mmotm 2021-12-29-20-07 uploaded SeongJae Park
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=3ad11107-30d8-ab75-961b-8142404c8c21@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sj@kernel.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;
as well as URLs for NNTP newsgroup(s).