From: Will Deacon <will.deacon@arm.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mhocko@suse.cz" <mhocko@suse.cz>,
Steve Capper <Steve.Capper@arm.com>,
Chris Metcalf <cmetcalf@tilera.com>
Subject: Re: [PATCH] mm: thp: Set the accessed flag for old pages on access fault.
Date: Mon, 1 Oct 2012 17:32:50 +0100 [thread overview]
Message-ID: <20121001163250.GO20812@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20121001145944.GA18051@redhat.com>
On Mon, Oct 01, 2012 at 03:59:44PM +0100, Andrea Arcangeli wrote:
> Hi Will,
Hi Andrea, Kirill,
Thanks for the comments.
> On Mon, Oct 01, 2012 at 02:51:45PM +0100, Will Deacon wrote:
> > +void huge_pmd_set_accessed(struct mm_struct *mm, struct vm_area_struct *vma,
> > + unsigned long address, pmd_t *pmd, pmd_t orig_pmd)
> > +{
> > + pmd_t entry;
> > +
> > + spin_lock(&mm->page_table_lock);
> > + entry = pmd_mkyoung(orig_pmd);
> > + if (pmdp_set_access_flags(vma, address & HPAGE_PMD_MASK, pmd, entry, 0))
> > + update_mmu_cache(vma, address, pmd);
>
> If the pmd is being splitted, this may not be a trasnhuge pmd anymore
> by the time you obtained the lock. (orig_pmd could be stale, and it
> wasn't verified with pmd_same either)
>
> The lock should be obtained through pmd_trans_huge_lock.
>
> if (pmd_trans_huge_lock(orig_pmd, vma) == 1)
> {
> set young bit
> spin_unlock(&mm->page_table_lock);
> }
I didn't notice that -- thanks. I'll move the locking outside of the
_set_accessed function and direct it via that function instead.
> On x86:
>
> int pmdp_set_access_flags(struct vm_area_struct *vma,
> unsigned long address, pmd_t *pmdp,
> pmd_t entry, int dirty)
> {
> int changed = !pmd_same(*pmdp, entry);
>
> VM_BUG_ON(address & ~HPAGE_PMD_MASK);
>
> if (changed && dirty) {
> *pmdp = entry;
>
> with dirty == 0 it looks like it won't make any difference, but I
> guess your arm pmdp_set_access_flag is different.
We use the generic code, which ignores the dirty argument. Still, we should
pass the correct value through anyway, so I'll fix that too.
> However it seems "dirty" means write access and so the invocation
> would better match the pte case:
>
> if (pmdp_set_access_flags(vma, address & HPAGE_PMD_MASK, pmd, entry,
> flags & FAULT_FLAG_WRITE))
>
>
> But note, you still have to update it even when "dirty" == 0, or it'll
> still infinite loop for read accesses.
Yup. v2 to follow once we've re-run our testing.
Cheers,
Will
--
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 prev parent reply other threads:[~2012-10-01 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 13:51 [PATCH] mm: thp: Set the accessed flag for old pages on access fault Will Deacon
2012-10-01 14:03 ` Kirill A. Shutemov
2012-10-01 14:59 ` Andrea Arcangeli
2012-10-01 16:32 ` Will Deacon [this message]
2012-10-16 9:37 ` Ni zhan Chen
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=20121001163250.GO20812@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Steve.Capper@arm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cmetcalf@tilera.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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).