From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: mm: dump: rework and fix
Date: Tue, 31 May 2016 14:49:00 +0100 [thread overview]
Message-ID: <1464702542-24394-1-git-send-email-mark.rutland@arm.com> (raw)
Hi Will,
Here are a couple of patches for the arm64 pagetable dump code.
The first patch is the final reusable ptdump patch, rebased to v4.7-rc1, as per
your request [1]. Other than the rebase, I have made no changes.
The second patch addresses an ambiguity in the dump output, in that we cannot
determine whether a span of block entries exists at the PGD, PUD, or PMD level.
It's logically unrelated to patch 1, and the two should apply independently,
but I've put them in a series so that I can call that out, and to avoid the
inevitable confusion with patches that appear to intersect.
I've given them both a spin on Juno R1 with v4.7-rc1 defconfig, fiddling with
the page size and number of levels. So far everything seems to work as
expected.
Thanks,
Mark.
[1] http://lkml.kernel.org/r/20160531132508.GJ24936 at arm.com
Mark Rutland (2):
arm64: mm: dump: make page table dumping reusable
arm64: mm: dump: log span level
arch/arm64/include/asm/ptdump.h | 44 +++++++++++++++++++++++++++++++++++++++++
arch/arm64/mm/dump.c | 40 +++++++++++++++++++++++++------------
2 files changed, 71 insertions(+), 13 deletions(-)
create mode 100644 arch/arm64/include/asm/ptdump.h
--
1.9.1
next reply other threads:[~2016-05-31 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 13:49 Mark Rutland [this message]
2016-05-31 13:49 ` [PATCH 1/2] arm64: mm: dump: make page table dumping reusable Mark Rutland
2016-06-01 3:01 ` Huang Shijie
2016-06-01 9:58 ` Mark Rutland
2016-06-02 1:48 ` Huang Shijie
2016-06-17 17:18 ` Catalin Marinas
2016-05-31 13:49 ` [PATCH 2/2] arm64: mm: dump: log span level Mark Rutland
2016-06-01 2:39 ` Huang Shijie
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=1464702542-24394-1-git-send-email-mark.rutland@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).