All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: fault: Print info about page table structure when dumping pte
Date: Tue, 30 May 2017 12:19:33 +0100	[thread overview]
Message-ID: <20170530111932.GF32289@arm.com> (raw)
In-Reply-To: <20170530111639.GB11653@leverpostej>

On Tue, May 30, 2017 at 12:16:39PM +0100, Mark Rutland wrote:
> On Tue, May 30, 2017 at 11:10:47AM +0100, Will Deacon wrote:
> > Whilst debugging a remote crash, I noticed that show_pte is unhelpful
> > when it comes to describing the structure of the page table being walked.
> > This is easily fixed by printing out the page table (swapper vs user),
> > page size and virtual address size when displaying the PGD address.
> > 
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
> > ---
> >  arch/arm64/mm/fault.c | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
> > index 37b95dff0b07..ee6085a922b6 100644
> > --- a/arch/arm64/mm/fault.c
> > +++ b/arch/arm64/mm/fault.c
> > @@ -89,7 +89,9 @@ void show_pte(struct mm_struct *mm, unsigned long addr)
> >  	if (!mm)
> >  		mm = &init_mm;
> >  
> > -	pr_alert("pgd = %p\n", mm->pgd);
> > +	pr_alert("%s pgtable: %luk pages, %u-bit VAs, pgd = %p\n",
> > +		 mm == &init_mm ? "swapper" : "user", PAGE_SIZE / SZ_1K,
> > +		 VA_BITS, mm->pgd);
> 
> I take it this will go with Kristina's fix [1] to dump the correct page
> table?

Yup, just waiting for her to respin those patches and I'll apply this one on
top.

> Otherwise, this would be more misleading than presently.
> 
> Assuming that is the case, this looks very useful to me. FWIW:
> 
> Acked-by: Mark Rutland <mark.rutland@arm.com>

Thanks,

Will

      reply	other threads:[~2017-05-30 11:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 10:10 [PATCH] arm64: fault: Print info about page table structure when dumping pte Will Deacon
2017-05-30 11:16 ` Mark Rutland
2017-05-30 11:19   ` Will Deacon [this message]

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=20170530111932.GF32289@arm.com \
    --to=will.deacon@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.