linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: steve.capper@linaro.org (Steve Capper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] ARM: mm: HugeTLB + THP support.
Date: Tue, 4 Jun 2013 14:13:22 +0100	[thread overview]
Message-ID: <20130604131320.GA17244@linaro.org> (raw)
In-Reply-To: <20130604130329.GR27516@mudshark.cambridge.arm.com>

On Tue, Jun 04, 2013 at 02:03:29PM +0100, Will Deacon wrote:
> On Tue, Jun 04, 2013 at 01:56:12PM +0100, Steve Capper wrote:
> > On Mon, Jun 03, 2013 at 11:40:11AM +0100, Steve Capper wrote:
> > > On Thu, May 23, 2013 at 04:31:16PM +0100, Steve Capper wrote:
> > > > The following patches bring both HugeTLB support and Transparent
> > > > HugePage (THP) support to ARM.
> > > > 
> > > > Only long descriptors (LPAE) are supported in this series.
> > > > 
> > > > The code has been tested on an Arndale board (Exynos 5250).
> > > > 
> > > > This patch set is based on 3.10-rc2.
> > > > 
> > > > Major changes since the Patch:
> > > >  * LPAE code has been separated from non-LPAE code (this series
> > > >    is the LPAE code).
> > > >  * PROT_NONE support for HugeTLB and THP has been implemented.
> > > > 
> > > > Major changes since the RFC:
> > > >  * huge pmd sharing removed from the 3-level code as this was
> > > >    found to be very rarely, if ever?, used. This allowed for some
> > > >    code simplification.
> > > > 
> > > >  * hardware pmd bits for 2-levels of paging are now taken from
> > > >    mmu.c. Also the mapping code now uses pte/pmd bit helper
> > > >    functions rather than the custom pre-processor logic.
> > > > 
> > > > Cheers,
> > > > -- 
> > > > Steve
> > > > 

[ ... ]

> > 
> > Just a polite ping on the above.
> > 
> > Are people happy to have this patch set merged?
> 
> Looks good to me, but worth checking that it doesn't conflict with the LPAE
> fixes I plan to send for 3.11 (since they're not terribly critical):
> 
>   https://git.kernel.org/cgit/linux/kernel/git/will/linux.git/log/?h=for-rmk/lpae
> 
> Of course, I can fix things up in my branch if necessary (just send me a
> pointer to your git repo).

Thanks, I'll take a look at the above now.

For reference these patches can be found at:
git://git.linaro.org/people/stevecapper/linux.git arm-hugepages-20130523

Cheers,
-- 
Steve

  reply	other threads:[~2013-06-04 13:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 15:31 [PATCH v2 0/4] ARM: mm: HugeTLB + THP support Steve Capper
2013-05-23 15:31 ` [PATCH v2 1/4] ARM: mm: correct pte_same behaviour for LPAE Steve Capper
2013-05-24 10:59   ` Catalin Marinas
2013-05-23 15:31 ` [PATCH v2 2/4] ARM: mm: Add support for flushing HugeTLB pages Steve Capper
2013-05-24 11:01   ` Catalin Marinas
2013-05-23 15:31 ` [PATCH v2 3/4] ARM: mm: HugeTLB support for LPAE systems Steve Capper
2013-05-24 11:03   ` Catalin Marinas
2013-05-28  8:59     ` Steve Capper
2013-05-23 15:31 ` [PATCH v2 4/4] ARM: mm: Transparent huge page " Steve Capper
2013-06-03 10:40 ` [PATCH v2 0/4] ARM: mm: HugeTLB + THP support Steve Capper
2013-06-04 12:56   ` Steve Capper
2013-06-04 13:03     ` Will Deacon
2013-06-04 13:13       ` Steve Capper [this message]
2013-06-04 14:37       ` Steve Capper

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=20130604131320.GA17244@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 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).