From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: benh@kernel.crashing.org, paulus@samba.org, dwg@au1.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc: split hugepage when using subpage protection
Date: Fri, 17 May 2013 14:06:36 +0530 [thread overview]
Message-ID: <8761yiuhnv.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1368778503-23230-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:
> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
>
> We find all the overlapping vma and mark them such that we don't allocate
> hugepage in that range. Also we split existing huge page so that the
> normal page hash can be invalidated and new page faulted in with new
> protection bits.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
> arch/powerpc/mm/subpage-prot.c | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/arch/powerpc/mm/subpage-prot.c b/arch/powerpc/mm/subpage-prot.c
> index 7c415dd..33fd329 100644
> --- a/arch/powerpc/mm/subpage-prot.c
> +++ b/arch/powerpc/mm/subpage-prot.c
> @@ -130,6 +130,14 @@ static void subpage_prot_clear(unsigned long addr, unsigned long len)
> up_write(&mm->mmap_sem);
> }
>
> +static int subpage_walk_pmd_entry(pmd_t *pmd, unsigned long addr,
> + unsigned long end, struct mm_walk *walk)
> +{
> + struct vm_area_struct *vma = walk->private;
> + split_huge_page_pmd(vma, addr, pmd);
> + return 0;
> +}
> +
> /*
> * Copy in a subpage protection map for an address range.
> * The map has 2 bits per 4k subpage, so 32 bits per 64k page.
> @@ -149,6 +157,12 @@ long sys_subpage_prot(unsigned long addr, unsigned long len, u32 __user *map)
> size_t nw;
> unsigned long next, limit;
> int err;
> + struct vm_area_struct *vma;
> +
> + struct mm_walk subpage_proto_walk = {
> + .mm = mm,
> + .pmd_entry = subpage_walk_pmd_entry,
> + };
>
> /* Check parameters */
> if ((addr & ~PAGE_MASK) || (len & ~PAGE_MASK) ||
> @@ -168,6 +182,19 @@ long sys_subpage_prot(unsigned long addr, unsigned long len, u32 __user *map)
> return -EFAULT;
>
> down_write(&mm->mmap_sem);
> +
> + /*
> + * We don't try too hard, we just mark all the vma in that range
> + * VM_NOHUGEPAGE and split them.
> + */
> + for (vma = find_vma(mm, addr);
> + (vma && vma->vm_end < (addr + len)); vma = vma->vm_next) {
should be, Missed commit -amend
(vma && vma->vm_start < (addr + len)); vma = vma->vm_next) {
> + vma->vm_flags |= VM_NOHUGEPAGE;
> + subpage_proto_walk.private = vma;
> + walk_page_range(vma->vm_start, vma->vm_end,
> + &subpage_proto_walk);
> + }
> for (limit = addr + len; addr < limit; addr = next) {
> next = pmd_addr_end(addr, limit);
> err = -ENOMEM;
-aneesh
next prev parent reply other threads:[~2013-05-17 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 8:15 [PATCH 1/2] powerpc: use smp_rmb when looking at deposisted pgtable to store hash index Aneesh Kumar K.V
2013-05-17 8:15 ` [PATCH 2/2] powerpc: split hugepage when using subpage protection Aneesh Kumar K.V
2013-05-17 8:36 ` Aneesh Kumar K.V [this message]
2013-05-20 1:18 ` [PATCH 1/2] powerpc: use smp_rmb when looking at deposisted pgtable to store hash index Michael Neuling
2013-05-20 4:27 ` Aneesh Kumar K.V
2013-05-20 6:28 ` Benjamin Herrenschmidt
2013-05-20 9:26 ` Aneesh Kumar K.V
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=8761yiuhnv.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=dwg@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).