[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150918070223.GA30505@free64-pc.asiapac.arm.com>
Date: Fri, 18 Sep 2015 15:02:23 +0800
From: Huang Shijie <shijie.huang@....com>
To: Jeremy Linton <jeremy.linton@....com>
Cc: linux-arm-kernel@...ts.infradead.org, catalin.marinas@....com,
will.deacon@....com, linux-kernel@...r.kernel.org,
dwoods@...ip.com, steve.capper@....com
Subject: Re: [PATCH 6/7] arm64: Make the kernel page dump utility aware of
the CONT bit
On Wed, Sep 16, 2015 at 02:03:05PM -0500, Jeremy Linton wrote:
Hi Jeremy,
> The kernel page dump utility needs to be aware of the CONT bit before
> it will break up pages ranges for display.
>
> Signed-off-by: Jeremy Linton <jeremy.linton@....com>
> ---
> arch/arm64/mm/dump.c | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/mm/dump.c b/arch/arm64/mm/dump.c
> index f3d6221..5a22a11 100644
> --- a/arch/arm64/mm/dump.c
> +++ b/arch/arm64/mm/dump.c
> @@ -67,6 +67,12 @@ static struct addr_marker address_markers[] = {
> { -1, NULL },
> };
>
> +/*
> + * The page dumper groups page table entries of the same type into a single
> + * description. It uses pg_state to track the range information while
> + * iterating over the pte entries. When the continuity is broken it then
> + * dumps out a description of the range.
> + */
> struct pg_state {
> struct seq_file *seq;
> const struct addr_marker *marker;
> @@ -114,6 +120,16 @@ static const struct prot_bits pte_bits[] = {
> .set = "NG",
> .clear = " ",
> }, {
> + .mask = PTE_CONT,
> + .val = PTE_CONT,
> + .set = "CON",
> + .clear = " ",
> + }, {
> + .mask = PTE_TABLE_BIT,
> + .val = PTE_TABLE_BIT,
> + .set = " ",
> + .clear = "BLK",
Please update the commit message, since your patch also add the TABLE_BIT, not
only the CONT bit.
thanks
Huang Shijie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists