From: Dirk Behme <dirk.behme@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Andre Przywara <Andre.Przywara@arm.com>,
sstabellini@kernel.org, Steve Capper <Steve.Capper@arm.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: ARMv8: New board bring up hangs in kernel start?
Date: Tue, 19 Apr 2016 15:59:28 +0200 [thread overview]
Message-ID: <571639C0.8010707@gmail.com> (raw)
In-Reply-To: <57149827.5030509@arm.com>
On 18.04.2016 10:17, Julien Grall wrote:
>
>
> On 16/04/2016 18:39, Dirk Behme wrote:
>> Hi Julien,
>
> Hi Dirk,
>
>>
>> On 06.04.2016 12:48, Julien Grall wrote:
>>>
>>> On 04/04/2016 16:44, Dirk Behme wrote:
>>>> Hi Julien,
>> I'm using
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/renesas/r8a7795.dtsi#n134
>>
>>
>>
>> The special thing here is that it has the offsets 0x10000, 0x20000,
>> 0x40000 and 0x60000. Instead of the standard ones 0x1000, 0x2000,
>> 0x4000
>> and 0x6000.
>
> Those offsets are normal, this platform seems to have a GIC using
> 64KB-aligned region rather than the classic 4KB-aligned one.
>
>> Now, just by try & error, using [1] makes things working.
>>
>> I'm not sure why this changes anything, though:
>>
>> * To my understanding, the GIC register ranges are max 0x1000. So I'd
>> think that the 0x2000 should be sufficient to map all necessary
>> registers.
>>
>> * I haven't observed any MMU fault. So it didn't look like any
>> non-mapped register was accessed without this change.
>
> Xen is checking if the platform is using an aliased GIC when the CPU
> interface size is 128KB (see gicv2_is_aliased and commit
> 21550029f709072aacf3b90edd574e7d3021b400).
>
> If you see "GICv2: Adjusting CPU interface base to..." then your GIC
> is aliased.
>
> In any case, the device-tree does not correctly describe the hardware
> on your platform. Can you send a patch to fix the upstream device-tree?
Done:
http://article.gmane.org/gmane.linux.kernel.renesas-soc/2951
Thanks!
Dirk
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-19 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 17:24 ARMv8: New board bring up hangs in kernel start? Dirk Behme
2016-03-23 18:41 ` Konrad Rzeszutek Wilk
2016-03-31 16:45 ` Stefano Stabellini
2016-03-29 18:53 ` Julien Grall
2016-03-31 17:41 ` Dirk Behme
2016-04-01 16:34 ` Julien Grall
2016-04-04 15:44 ` Dirk Behme
2016-04-06 10:48 ` Julien Grall
2016-04-16 17:39 ` Dirk Behme
2016-04-18 8:17 ` Julien Grall
2016-04-19 13:59 ` Dirk Behme [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=571639C0.8010707@gmail.com \
--to=dirk.behme@gmail.com \
--cc=Andre.Przywara@arm.com \
--cc=Steve.Capper@arm.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.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).