From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 2/3] arm64: Add support for ARCH_SUPPORTS_DEBUG_PAGEALLOC
Date: Wed, 10 Feb 2016 10:54:54 +0000 [thread overview]
Message-ID: <20160210105453.GB2632@leverpostej> (raw)
In-Reply-To: <20160210103814.GC13577@e104818-lin.cambridge.arm.com>
On Wed, Feb 10, 2016 at 10:38:14AM +0000, Catalin Marinas wrote:
> On Fri, Feb 05, 2016 at 04:24:47PM -0800, Laura Abbott wrote:
> > --- a/arch/arm64/mm/mmu.c
> > +++ b/arch/arm64/mm/mmu.c
> > @@ -149,6 +149,19 @@ static void split_pud(pud_t *old_pud, pmd_t *pmd)
> > } while (pmd++, i++, i < PTRS_PER_PMD);
> > }
> >
> > +bool block_mappings_allowed(phys_addr_t (*pgtable_alloc)(void))
> > +{
> > +
> > + /*
> > + * If debug_page_alloc is enabled we must map the linear map
> > + * using pages. However, other mappings created by
> > + * create_mapping_noalloc must use sections in some cases. Allow
> > + * sections to be used in those cases, where no pgtable_alloc
> > + * function is provided.
> > + */
> > + return !pgtable_alloc || !debug_pagealloc_enabled();
> > +}
>
> This breaks the build when CONFIG_DEBUG_PAGEALLOC is not enabled
> (defconfig) since debug_pagealloc_enabled() is not defined. A fix went
> in next/master as commit 0987684b855c
> ("mm-slab-clean-up-debug_pagealloc-processing-code-fix"). I need to
> track it down and merge it via the arm64 tree, otherwise I'll add some
> #ifdefs in this function.
In the cover for v2 [1], it was mentioend that we needed a patch [2]
"mm: provide debug_pagealloc_enabled() without CONFIG_DEBUG_PAGEALLOC".
I assumed that was already queued via the mm tree.
> BTW, shouldn't the block_mappings_allowed() function be static?
That would make sense to me, yes.
Mark.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/403439.html
[2] http://article.gmane.org/gmane.linux.kernel.mm/1452
next prev parent reply other threads:[~2016-02-10 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 0:24 [PATCHv4 0/3] ARCH_SUPPORTS_DEBUG_PAGEALLOC for arm64 Laura Abbott
2016-02-06 0:24 ` [PATCHv4 1/3] arm64: Drop alloc function from create_mapping Laura Abbott
2016-02-06 0:24 ` [PATCHv4 2/3] arm64: Add support for ARCH_SUPPORTS_DEBUG_PAGEALLOC Laura Abbott
2016-02-10 10:38 ` Catalin Marinas
2016-02-10 10:40 ` Ard Biesheuvel
2016-02-10 10:54 ` Mark Rutland [this message]
2016-02-10 11:02 ` Catalin Marinas
2016-02-06 0:24 ` [PATCHv4 3/3] arm64: ptdump: Indicate whether memory should be faulting Laura Abbott
2016-02-09 12:19 ` [PATCHv4 0/3] ARCH_SUPPORTS_DEBUG_PAGEALLOC for arm64 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=20160210105453.GB2632@leverpostej \
--to=mark.rutland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox