linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
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 15:49:00 +0100	[thread overview]
Message-ID: <55F1985C.8050602@arm.com> (raw)
In-Reply-To: <55F193BE.90608@citrix.com>

On 10/09/15 15:29, Julien Grall wrote:
> On 10/09/15 14:01, Marc Zyngier wrote:
>> Hi Julien,
>>
>> On 09/09/15 18:21, Julien Grall wrote:
>>> Hi Catalin,
>>>
>>> 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.
>>>
>>> Do you have any insight for debugging this problem?
>>
>> I've just given it a good shake on the Mustang we have here, and I'm not
>> experiencing anything like this. Any chance you could print out the
>> ID_AA64MMFR1_EL1 register value, just in case?
> 
> The value of ID_AA64MMFR1_EL1 is 0000000000000000
> 
> I'm using Debian Jessie for the userspace with an LVM partition for the
> home. U-boot is used to boot the kernel.

Similar setup here (except for LVM). The box seems quite solid (multiple
kernel compiles, and nothing is screaming).

My u-boot says:

CPU0: APM ARM 64-bit Potenza Rev A3 2400MHz PCP 2400MHz
     32 KB ICACHE, 32 KB DCACHE
     SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz

How does this compares to yours?

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2015-09-10 14:49 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
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 [this message]
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=55F1985C.8050602@arm.com \
    --to=marc.zyngier@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).