From: "Shi, Yang" <yang.shi@linaro.org>
To: Hugh Dickins <hughd@google.com>
Cc: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
aarcange@redhat.com, mgorman@suse.de,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] mm: move huge_pmd_set_accessed out of huge_memory.c
Date: Thu, 21 Apr 2016 15:57:35 -0700 [thread overview]
Message-ID: <57195ADF.6080808@linaro.org> (raw)
In-Reply-To: <alpine.LSU.2.11.1604210200430.5164@eggly.anvils>
On 4/21/2016 2:15 AM, Hugh Dickins wrote:
> On Wed, 20 Apr 2016, Shi, Yang wrote:
>
>> Hi folks,
>>
>> I didn't realize pmd_* functions are protected by CONFIG_TRANSPARENT_HUGEPAGE
>> on the most architectures before I made this change.
>>
>> Before I fix all the affected architectures code, I want to check if you guys
>> think this change is worth or not?
>
> Thanks for asking: no, it is not worthwhile.
>
> I would much prefer not to have to consider these trivial cleanups
> in the huge memory area at this time. Kirill and I have urgent work
> to do in this area, and coping with patch conflicts between different
> versions of the source will not help any of us.
Thanks for your suggestion. I would consider to put such cleanup work on
the back burner.
Yang
>
> Thanks,
> Hugh
>
>>
>> Thanks,
>> Yang
>>
>> On 4/20/2016 11:24 AM, Yang Shi wrote:
>>> huge_pmd_set_accessed is only called by __handle_mm_fault from memory.c,
>>> move the definition to memory.c and make it static like create_huge_pmd and
>>> wp_huge_pmd.
>>>
>>> Signed-off-by: Yang Shi <yang.shi@linaro.org>
>>> ---
>>> include/linux/huge_mm.h | 4 ----
>>> mm/huge_memory.c | 23 -----------------------
>>> mm/memory.c | 23 +++++++++++++++++++++++
>>> 3 files changed, 23 insertions(+), 27 deletions(-)
>>>
>>> diff --git a/include/linux/huge_mm.h b/include/linux/huge_mm.h
>>> index 7008623..c218ab7b 100644
>>> --- a/include/linux/huge_mm.h
>>> +++ b/include/linux/huge_mm.h
>>> @@ -8,10 +8,6 @@ extern int do_huge_pmd_anonymous_page(struct mm_struct
>>> *mm,
>>> extern int copy_huge_pmd(struct mm_struct *dst_mm, struct mm_struct
>>> *src_mm,
>>> pmd_t *dst_pmd, pmd_t *src_pmd, unsigned long addr,
>>> struct vm_area_struct *vma);
>>> -extern void huge_pmd_set_accessed(struct mm_struct *mm,
>>> - struct vm_area_struct *vma,
>>> - unsigned long address, pmd_t *pmd,
>>> - pmd_t orig_pmd, int dirty);
>>> extern int do_huge_pmd_wp_page(struct mm_struct *mm, struct
>>> vm_area_struct *vma,
>>> unsigned long address, pmd_t *pmd,
>>> pmd_t orig_pmd);
>>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>>> index fecbbc5..6c14cb6 100644
>>> --- a/mm/huge_memory.c
>>> +++ b/mm/huge_memory.c
>>> @@ -1137,29 +1137,6 @@ out:
>>> return ret;
>>> }
>>>
>>> -void huge_pmd_set_accessed(struct mm_struct *mm,
>>> - struct vm_area_struct *vma,
>>> - unsigned long address,
>>> - pmd_t *pmd, pmd_t orig_pmd,
>>> - int dirty)
>>> -{
>>> - spinlock_t *ptl;
>>> - pmd_t entry;
>>> - unsigned long haddr;
>>> -
>>> - ptl = pmd_lock(mm, pmd);
>>> - if (unlikely(!pmd_same(*pmd, orig_pmd)))
>>> - goto unlock;
>>> -
>>> - entry = pmd_mkyoung(orig_pmd);
>>> - haddr = address & HPAGE_PMD_MASK;
>>> - if (pmdp_set_access_flags(vma, haddr, pmd, entry, dirty))
>>> - update_mmu_cache_pmd(vma, address, pmd);
>>> -
>>> -unlock:
>>> - spin_unlock(ptl);
>>> -}
>>> -
>>> static int do_huge_pmd_wp_page_fallback(struct mm_struct *mm,
>>> struct vm_area_struct *vma,
>>> unsigned long address,
>>> diff --git a/mm/memory.c b/mm/memory.c
>>> index 93897f2..6ced4eb 100644
>>> --- a/mm/memory.c
>>> +++ b/mm/memory.c
>>> @@ -3287,6 +3287,29 @@ static int wp_huge_pmd(struct mm_struct *mm, struct
>>> vm_area_struct *vma,
>>> return VM_FAULT_FALLBACK;
>>> }
>>>
>>> +static void huge_pmd_set_accessed(struct mm_struct *mm,
>>> + struct vm_area_struct *vma,
>>> + unsigned long address,
>>> + pmd_t *pmd, pmd_t orig_pmd,
>>> + int dirty)
>>> +{
>>> + spinlock_t *ptl;
>>> + pmd_t entry;
>>> + unsigned long haddr;
>>> +
>>> + ptl = pmd_lock(mm, pmd);
>>> + if (unlikely(!pmd_same(*pmd, orig_pmd)))
>>> + goto unlock;
>>> +
>>> + entry = pmd_mkyoung(orig_pmd);
>>> + haddr = address & HPAGE_PMD_MASK;
>>> + if (pmdp_set_access_flags(vma, haddr, pmd, entry, dirty))
>>> + update_mmu_cache_pmd(vma, address, pmd);
>>> +
>>> +unlock:
>>> + spin_unlock(ptl);
>>> +}
>>> +
>>> /*
>>> * These routines also need to handle stuff like marking pages dirty
>>> * and/or accessed for architectures that don't do it in hardware (most
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-04-21 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 18:24 [PATCH] mm: move huge_pmd_set_accessed out of huge_memory.c Yang Shi
2016-04-20 19:04 ` kbuild test robot
2016-04-20 19:09 ` kbuild test robot
2016-04-20 19:20 ` kbuild test robot
2016-04-20 21:00 ` Shi, Yang
2016-04-21 7:30 ` Kirill A. Shutemov
2016-04-21 22:56 ` Shi, Yang
2016-04-22 9:48 ` Kirill A. Shutemov
2016-04-29 18:09 ` Shi, Yang
2016-04-21 9:15 ` Hugh Dickins
2016-04-21 22:57 ` Shi, Yang [this message]
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=57195ADF.6080808@linaro.org \
--to=yang.shi@linaro.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@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;
as well as URLs for NNTP newsgroup(s).