All of lore.kernel.org
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add support for hardware updates of the access and dirty pte bits
Date: Thu, 10 Sep 2015 11:07:54 +0100	[thread overview]
Message-ID: <20150910100753.GE12294@localhost> (raw)
In-Reply-To: <55F06A87.3000204@citrix.com>

On Wed, Sep 09, 2015 at 06:21:11PM +0100, Julien Grall wrote:
> I've tried to boot the latest linus/master (a794b4f) which include this
> patch as DOM0 on xgene. This is failing late in the boot with
> a BUG (see trace below).
> 
> The bisector pointed me to this patch. When I disable
> CONFIG_ARM64_HW_AFDBM, I'm able to boot the kernel and use it
> without any issue.
> 
> Although, I'm not sure to understand how this patch could
> possibly break the filesystem subsystem.

I don't understand either. It seems that the kernel raises a BUG on
!PagePrivate but this patch never touches the page structure, only ptes.

I recall to have tested it on XGene but I can try it again (bare metal).
Is the bare metal error for you the same?

> Do you have any insight for debugging this problem?
[...]
> > diff --git a/arch/arm64/mm/proc.S b/arch/arm64/mm/proc.S
> > index 39139a3aa16d..a8be513dff6f 100644
> > --- a/arch/arm64/mm/proc.S
> > +++ b/arch/arm64/mm/proc.S
> > @@ -196,6 +196,19 @@ ENTRY(__cpu_setup)
> >  	 */
> >  	mrs	x9, ID_AA64MMFR0_EL1
> >  	bfi	x10, x9, #32, #3
> > +#ifdef CONFIG_ARM64_HW_AFDBM
> > +	/*
> > +	 * Hardware update of the Access and Dirty bits.
> > +	 */
> > +	mrs	x9, ID_AA64MMFR1_EL1
> > +	and	x9, x9, #0xf
> > +	cbz	x9, 2f
> > +	cmp	x9, #2
> > +	b.lt	1f
> > +	orr	x10, x10, #TCR_HD		// hardware Dirty flag update
> > +1:	orr	x10, x10, #TCR_HA		// hardware Access flag update
> > +2:
> > +#endif	/* CONFIG_ARM64_HW_AFDBM */
> >  	msr	tcr_el1, x10
> >  	ret					// return to head.S
> >  ENDPROC(__cpu_setup)

Just in case some ID registers are wrong, can you do an "#if 0" above
instead of CONFIG_ARM64_HW_AFDBM?

-- 
Catalin

  parent reply	other threads:[~2015-09-10 10:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 16:24 [PATCH] arm64: Add support for hardware updates of the access and dirty pte bits Catalin Marinas
2015-09-09 17:21 ` Julien Grall
2015-09-09 18:22   ` Mark Rutland
2015-09-09 18:27     ` Julien Grall
2015-09-10 10:07   ` Catalin Marinas [this message]
2015-09-10 10:41     ` Will Deacon
2015-09-10 14:45     ` Julien Grall
2015-09-10 14:54       ` Marc Zyngier
2015-09-10 15:10         ` Julien Grall
2015-09-10 15:21           ` Marc Zyngier
2015-09-10 15:38       ` Will Deacon
2015-09-11 15:43         ` Julien Grall
2015-09-10 13:01   ` Marc Zyngier
2015-09-10 14:29     ` Julien Grall
2015-09-10 14:49       ` Marc Zyngier
2015-09-10 14:58         ` Julien Grall

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=20150910100753.GE12294@localhost \
    --to=catalin.marinas@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.