From: "Hillf Danton" <hillf.zj@alibaba-inc.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: [PATCHv9-rebased2 11/37] mm: introduce do_set_pmd()
Date: Thu, 16 Jun 2016 17:15:22 +0800 [thread overview]
Message-ID: <050301d1c7af$9cbe81b0$d63b8510$@alibaba-inc.com> (raw)
In-Reply-To: <050201d1c7ae$9dbf9370$d93eba50$@alibaba-inc.com>
> +
> +static int do_set_pmd(struct fault_env *fe, struct page *page)
> +{
> + struct vm_area_struct *vma = fe->vma;
> + bool write = fe->flags & FAULT_FLAG_WRITE;
> + unsigned long haddr = fe->address & HPAGE_PMD_MASK;
> + pmd_t entry;
> + int i, ret;
> +
> + if (!transhuge_vma_suitable(vma, haddr))
> + return VM_FAULT_FALLBACK;
> +
> + ret = VM_FAULT_FALLBACK;
> + page = compound_head(page);
> +
> + fe->ptl = pmd_lock(vma->vm_mm, fe->pmd);
> + if (unlikely(!pmd_none(*fe->pmd)))
> + goto out;
Can we reply to the caller that fault is handled correctly(by
resetting ret to zero before jump)?
> +
> + for (i = 0; i < HPAGE_PMD_NR; i++)
> + flush_icache_page(vma, page + i);
> +
> + entry = mk_huge_pmd(page, vma->vm_page_prot);
> + if (write)
> + entry = maybe_pmd_mkwrite(pmd_mkdirty(entry), vma);
> +
> + add_mm_counter(vma->vm_mm, MM_FILEPAGES, HPAGE_PMD_NR);
> + page_add_file_rmap(page, true);
> +
> + set_pmd_at(vma->vm_mm, haddr, fe->pmd, entry);
> +
> + update_mmu_cache_pmd(vma, haddr, fe->pmd);
> +
> + /* fault is handled */
> + ret = 0;
> +out:
> + spin_unlock(fe->ptl);
> + return ret;
> +}
> +#else
> +static int do_set_pmd(struct fault_env *fe, struct page *page)
> +{
> + BUILD_BUG();
> + return 0;
> +}
> +#endif
> +
> /**
> * alloc_set_pte - setup new PTE entry for given page and add reverse page
> * mapping. If needed, the fucntion allocates page table or use pre-allocated.
> @@ -2940,9 +3000,19 @@ int alloc_set_pte(struct fault_env *fe, struct mem_cgroup *memcg,
> struct vm_area_struct *vma = fe->vma;
> bool write = fe->flags & FAULT_FLAG_WRITE;
> pte_t entry;
> + int ret;
> +
> + if (pmd_none(*fe->pmd) && PageTransCompound(page)) {
> + /* THP on COW? */
> + VM_BUG_ON_PAGE(memcg, page);
> +
> + ret = do_set_pmd(fe, page);
> + if (ret != VM_FAULT_FALLBACK)
> + return ret;
> + }
>
> if (!fe->pte) {
> - int ret = pte_alloc_one_map(fe);
> + ret = pte_alloc_one_map(fe);
> if (ret)
> return ret;
> }
> diff --git a/mm/migrate.c b/mm/migrate.c
--
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>
next parent reply other threads:[~2016-06-16 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <050201d1c7ae$9dbf9370$d93eba50$@alibaba-inc.com>
2016-06-16 9:15 ` Hillf Danton [this message]
2016-06-16 10:17 ` Kirill A. Shutemov
2016-06-06 14:06 [PATCHv9 00/32] THP-enabled tmpfs/shmem using compound pages Kirill A. Shutemov
2016-06-15 20:06 ` [PATCHv9-rebased2 00/37] " Kirill A. Shutemov
2016-06-15 20:06 ` [PATCHv9-rebased2 11/37] mm: introduce do_set_pmd() 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='050301d1c7af$9cbe81b0$d63b8510$@alibaba-inc.com' \
--to=hillf.zj@alibaba-inc.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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