linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@fedoraproject.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Laura Abbott <labbott@fedoraproject.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCHv2 0/3] ARCH_SUPPORTS_DEBUG_PAGEALLOC for arm64
Date: Fri, 29 Jan 2016 15:46:55 -0800	[thread overview]
Message-ID: <1454111218-3461-1-git-send-email-labbott@fedoraproject.org> (raw)

Hi,

This is v2 of the series to add proper debug pagealloc support for arm64.

Changes since v1:
- Dropped the config for forcing pages and changed it to runtime detection.
  This now matches better with how x86 and other arches are being updated.
  That patch is now dropped completely and folded in to the actual patch
  for ARCH_SUPPORTS_DEBUG_PAGEALLOC
- Took Mark's suggestion to rename create_mapping -> create_mapping_noalloc
- The only way to get all PAGE_SIZE mappings right now is to enable
  debug_pagealloc. This is the only actual use case right now. It is fairly
  simple to add the code to let this happen for other uses. If that
  time comes someone can plead their case to the court of ARM to accept such
  a patch.

This series now depends on the patch to let debug_pagealloc_enabled()
be used when !CONFIG_DEBUG_PAGEALLOC
(http://article.gmane.org/gmane.linux.kernel.mm/145208)
I can either take acks and submit this to the MM tree or we can wait for that
patch to show up in something I can rebase to.

Thanks,
Laura

Laura Abbott (3):
  arm64: Drop alloc function from create_mapping
  arm64: Add support for ARCH_SUPPORTS_DEBUG_PAGEALLOC
  arm64: ptdump: Indicate whether memory should be faulting

 arch/arm64/Kconfig       |  3 +++
 arch/arm64/mm/dump.c     |  5 +++++
 arch/arm64/mm/mmu.c      | 37 +++++++++++++++++++++++++------------
 arch/arm64/mm/pageattr.c | 40 +++++++++++++++++++++++++++++++++-------
 4 files changed, 66 insertions(+), 19 deletions(-)

-- 
2.5.0

             reply	other threads:[~2016-01-29 23:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 23:46 Laura Abbott [this message]
2016-01-29 23:46 ` [PATCHv2 1/3] arm64: Drop alloc function from create_mapping Laura Abbott
2016-01-30 10:34   ` Ard Biesheuvel
2016-02-01 12:11     ` Mark Rutland
2016-01-29 23:46 ` [PATCHv2 2/3] arm64: Add support for ARCH_SUPPORTS_DEBUG_PAGEALLOC Laura Abbott
2016-02-01 12:29   ` Mark Rutland
2016-02-01 21:24     ` Laura Abbott
2016-02-02  8:57       ` Ard Biesheuvel
2016-02-02 12:23       ` Mark Rutland
2016-02-02 12:31         ` Mark Rutland
2016-02-02 16:08           ` Laura Abbott
2016-01-29 23:46 ` [PATCHv2 3/3] arm64: ptdump: Indicate whether memory should be faulting Laura Abbott

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=1454111218-3461-1-git-send-email-labbott@fedoraproject.org \
    --to=labbott@fedoraproject.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=will.deacon@arm.com \
    /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).