From: Dmitry Osipenko <digetx@gmail.com>
To: Wei Yang <richard.weiyang@linux.alibaba.com>,
akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
vbabka@suse.cz, yang.shi@linux.alibaba.com,
thomas_os@shipmail.org, anshuman.khandual@arm.com,
sean.j.christopherson@intel.com, peterx@redhat.com,
aneesh.kumar@linux.ibm.com, willy@infradead.org,
thellstrom@vmware.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Patch v4 0/4] mm/mremap: cleanup move_page_tables() a little
Date: Thu, 9 Jul 2020 22:38:58 +0300 [thread overview]
Message-ID: <3cab86b0-586e-781b-1620-f28b00c57d44@gmail.com> (raw)
In-Reply-To: <20200708095028.41706-1-richard.weiyang@linux.alibaba.com>
08.07.2020 12:50, Wei Yang пишет:
> move_page_tables() tries to move page table by PMD or PTE.
>
> The root reason is if it tries to move PMD, both old and new range should be
> PMD aligned. But current code calculate old range and new range separately.
> This leads to some redundant check and calculation.
>
> This cleanup tries to consolidate the range check in one place to reduce some
> extra range handling.
>
> v4:
> * remove a redundant parentheses pointed by Kirill
>
> v3:
> * merge patch 1 with 2 as suggested by Kirill
> * add patch 4 to simplify the logic to calculate next and extent
Hello, Wei!
Unfortunately you re-introduced the offending change that was fixed in
v2 and today's next-20200709 on ARM32 is broken once again:
BUG: Bad rss-counter state mm:db85ec46 type:MM_ANONPAGES val:190
Please don't do it ;)
> v2:
> * remove 3rd patch which doesn't work on ARM platform. Thanks report and
> test from Dmitry Osipenko
>
> Wei Yang (4):
> mm/mremap: it is sure to have enough space when extent meets
> requirement
> mm/mremap: calculate extent in one place
> mm/mremap: start addresses are properly aligned
> mm/mremap: use pmd_addr_end to simplify the calculate of extent
>
> include/linux/huge_mm.h | 2 +-
> mm/huge_memory.c | 8 +-------
> mm/mremap.c | 27 ++++++++++-----------------
> 3 files changed, 12 insertions(+), 25 deletions(-)
>
next prev parent reply other threads:[~2020-07-09 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 9:50 Wei Yang
2020-07-08 9:50 ` [Patch v4 1/4] mm/mremap: it is sure to have enough space when extent meets requirement Wei Yang
2020-07-08 9:50 ` [Patch v4 2/4] mm/mremap: calculate extent in one place Wei Yang
2020-07-08 9:50 ` [Patch v4 3/4] mm/mremap: start addresses are properly aligned Wei Yang
2020-07-08 9:50 ` [Patch v4 4/4] mm/mremap: use pmd_addr_end to simplify the calculate of extent Wei Yang
2020-07-09 19:38 ` Dmitry Osipenko [this message]
2020-07-10 1:14 ` [Patch v4 0/4] mm/mremap: cleanup move_page_tables() a little Wei Yang
2020-07-10 8:14 ` Kirill A. Shutemov
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=3cab86b0-586e-781b-1620-f28b00c57d44@gmail.com \
--to=digetx@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anshuman.khandual@arm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=richard.weiyang@linux.alibaba.com \
--cc=sean.j.christopherson@intel.com \
--cc=thellstrom@vmware.com \
--cc=thomas_os@shipmail.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.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