From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 3/3] arm64: ptdump: Indicate whether memory should be faulting
Date: Fri, 5 Feb 2016 14:34:04 +0000 [thread overview]
Message-ID: <20160205143403.GD19614@leverpostej> (raw)
In-Reply-To: <1454615017-24672-4-git-send-email-labbott@fedoraproject.org>
On Thu, Feb 04, 2016 at 11:43:37AM -0800, Laura Abbott wrote:
>
> With CONFIG_DEBUG_PAGEALLOC, pages do not have the valid bit
> set when free in the buddy allocator. Add an indiciation to
> the page table dumping code that the valid bit is not set,
> 'F' for fault, to make this easier to understand.
>
> Signed-off-by: Laura Abbott <labbott@fedoraproject.org>
This looks sensible to me, and worked in testing.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Tested-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> arch/arm64/mm/dump.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm64/mm/dump.c b/arch/arm64/mm/dump.c
> index 5a22a11..f381ac9 100644
> --- a/arch/arm64/mm/dump.c
> +++ b/arch/arm64/mm/dump.c
> @@ -90,6 +90,11 @@ struct prot_bits {
>
> static const struct prot_bits pte_bits[] = {
> {
> + .mask = PTE_VALID,
> + .val = PTE_VALID,
> + .set = " ",
> + .clear = "F",
> + }, {
> .mask = PTE_USER,
> .val = PTE_USER,
> .set = "USR",
> --
> 2.5.0
>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Laura Abbott <labbott@fedoraproject.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 3/3] arm64: ptdump: Indicate whether memory should be faulting
Date: Fri, 5 Feb 2016 14:34:04 +0000 [thread overview]
Message-ID: <20160205143403.GD19614@leverpostej> (raw)
In-Reply-To: <1454615017-24672-4-git-send-email-labbott@fedoraproject.org>
On Thu, Feb 04, 2016 at 11:43:37AM -0800, Laura Abbott wrote:
>
> With CONFIG_DEBUG_PAGEALLOC, pages do not have the valid bit
> set when free in the buddy allocator. Add an indiciation to
> the page table dumping code that the valid bit is not set,
> 'F' for fault, to make this easier to understand.
>
> Signed-off-by: Laura Abbott <labbott@fedoraproject.org>
This looks sensible to me, and worked in testing.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Tested-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> arch/arm64/mm/dump.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm64/mm/dump.c b/arch/arm64/mm/dump.c
> index 5a22a11..f381ac9 100644
> --- a/arch/arm64/mm/dump.c
> +++ b/arch/arm64/mm/dump.c
> @@ -90,6 +90,11 @@ struct prot_bits {
>
> static const struct prot_bits pte_bits[] = {
> {
> + .mask = PTE_VALID,
> + .val = PTE_VALID,
> + .set = " ",
> + .clear = "F",
> + }, {
> .mask = PTE_USER,
> .val = PTE_USER,
> .set = "USR",
> --
> 2.5.0
>
next prev parent reply other threads:[~2016-02-05 14:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1454615017-24672-1-git-send-email-labbott@fedoraproject.org>
2016-02-04 19:43 ` [PATCHv3 1/3] arm64: Drop alloc function from create_mapping Laura Abbott
2016-02-04 19:43 ` Laura Abbott
2016-02-04 19:43 ` [PATCHv2 2/3] arm64: Add support for ARCH_SUPPORTS_DEBUG_PAGEALLOC Laura Abbott
2016-02-04 19:43 ` Laura Abbott
2016-02-05 12:05 ` Ard Biesheuvel
2016-02-05 12:05 ` Ard Biesheuvel
2016-02-05 14:20 ` Mark Rutland
2016-02-05 14:20 ` Mark Rutland
2016-02-06 0:08 ` Laura Abbott
2016-02-06 0:08 ` Laura Abbott
2016-02-04 19:43 ` [PATCHv3 3/3] arm64: ptdump: Indicate whether memory should be faulting Laura Abbott
2016-02-04 19:43 ` Laura Abbott
2016-02-05 12:05 ` Ard Biesheuvel
2016-02-05 12:05 ` Ard Biesheuvel
2016-02-05 14:34 ` Mark Rutland [this message]
2016-02-05 14:34 ` Mark Rutland
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=20160205143403.GD19614@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 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.