From: steve.capper@linaro.org (Steve Capper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64: Use pte manipulation functions for THP
Date: Wed, 12 Feb 2014 09:43:39 +0000 [thread overview]
Message-ID: <20140212094338.GA11325@linaro.org> (raw)
In-Reply-To: <1391696171-8922-1-git-send-email-steve.capper@linaro.org>
On Thu, Feb 06, 2014 at 02:16:08PM +0000, Steve Capper wrote:
> This series replaces the Transparent HugePage pmd manipulation
> functions with calls to the standard pte functions. This allows the THP
> code to take advantage of the new PTE_WRITE logic, and provides better
> parity with the HugeTLB code (which already uses the pte functions).
>
> Testing was done on the Fast Model with LTP THP tests, and the 3.14-rc1
> kernel was used.
Hi,
Does this series look reasonable?
Thanks,
--
Steve
>
> Steve Capper (3):
> arm64: mm: Remove PMD_BIT_FUNC macro
> arm64: mm: Route pmd thp functions through pte equivalents
> arm64: mm: Correct definition of pmd_mknotpresent
>
> arch/arm64/include/asm/pgtable.h | 91 +++++++++++++++++++++++++++-------------
> 1 file changed, 62 insertions(+), 29 deletions(-)
>
> --
> 1.8.1.4
>
next prev parent reply other threads:[~2014-02-12 9:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 14:16 [PATCH 0/3] arm64: Use pte manipulation functions for THP Steve Capper
2014-02-06 14:16 ` [PATCH 1/3] arm64: mm: Remove PMD_BIT_FUNC macro Steve Capper
2014-02-06 14:16 ` [PATCH 2/3] arm64: mm: Route pmd thp functions through pte equivalents Steve Capper
2014-02-12 10:14 ` Catalin Marinas
2014-02-12 10:32 ` Steve Capper
2014-02-20 17:00 ` Catalin Marinas
2014-02-06 14:16 ` [PATCH 3/3] arm64: mm: Correct definition of pmd_mknotpresent Steve Capper
2014-02-12 9:43 ` Steve Capper [this message]
2014-02-12 10:07 ` [PATCH 0/3] arm64: Use pte manipulation functions for THP Will Deacon
2014-02-12 10:16 ` Catalin Marinas
2014-02-12 10:21 ` Will Deacon
2014-02-12 11:50 ` Steve Capper
2014-02-12 12:43 ` Russell King - ARM Linux
2014-02-12 13:47 ` Catalin Marinas
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=20140212094338.GA11325@linaro.org \
--to=steve.capper@linaro.org \
--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.