From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/2] Fixes for contiguous hugetlb
Date: Mon, 24 Sep 2018 17:25:50 +0100 [thread overview]
Message-ID: <20180924162549.GC12461@arm.com> (raw)
In-Reply-To: <20180921153405.10090-1-steve.capper@arm.com>
On Fri, Sep 21, 2018 at 04:34:03PM +0100, Steve Capper wrote:
> This patch series addresses a couple of issues found with contiguous hugetlb.
>
> 1) It is possible for old hugetlb's to be created by remove_migration_pte, the
> first patch adjusts the code to capture any young ptes that could have been
> created by hardware dirty bit management.
>
> 2) huge_ptep_set_access_flags has been changed in the second patch to prevent it
> from unnecessarily invalidating contiguous hugetlb mappings (which also stops
> it from potentially evoking back-to-back page faults).
Thanks Steve, these look good to me. I'll pick them up as fixes.
Will
prev parent reply other threads:[~2018-09-24 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 15:34 [PATCH V2 0/2] Fixes for contiguous hugetlb Steve Capper
2018-09-21 15:34 ` [PATCH V2 1/2] arm64: hugetlb: Fix handling of young ptes Steve Capper
2018-09-21 15:34 ` [PATCH V2 2/2] arm64: hugetlb: Avoid unnecessary clearing in huge_ptep_set_access_flags Steve Capper
2018-09-24 16:25 ` Will Deacon [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=20180924162549.GC12461@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.