All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: "Ferger, Max" <M.Ferger@KOSTAL.COM>,
	Ian Campbell <ian.campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>,
	Iurii Konovalenko <iurii.konovalenko@globallogic.com>
Subject: Re: Dom0 kernel for Xen4.6 on R-Car H2 (LAGER)
Date: Tue, 20 Oct 2015 22:44:10 +0100	[thread overview]
Message-ID: <5626B5AA.6060304@citrix.com> (raw)
In-Reply-To: <f00c7ece34cb4a10bead5faaa42079aa@DEBEMAIL001.kostal.int>

Hi,

On 20/10/2015 12:23, Ferger, Max wrote:
> One step closer, thanks again!
>
> Removing the incompatible PCI/USB devices lets Xen boot somewhat further.
>
> Here is the (significant) difference in log output, the full new one is appended.
>
> I've back traced the trap message from traps.c +2447:
> None of the explicit 'goto bad_data_abort;' calls is responsible, but a fall through via traps.c +2444.

> +(XEN) traps.c:2447:d0v0 HSR=0x93830007 pc=0xc001e398 gva=0xe7804060 gpa=0x000000e6160060

This traps likely means that DOM0 is trying to access a region which is 
not mapped in stage-2.

In the log GPA is the physical address expected. You can give a look to
the datasheet of your platform to find the corresponding region.

Looking to this GPA, it's used in 
arch/arm/mach-shmobile/setup-rcar-gen2.c to read the mode pins and the 
region is not described in the DT. You will have to map it manually in 
Xen. Give a look to how it's done for omap5 (see omap5_specific_mapping).

BTW, I got confirmation by a person working on this board that there may 
be more regions not described in DT. Although, I don't know all of them :(.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-10-20 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 14:17 Dom0 kernel for Xen4.6 on R-Car H2 (LAGER) Ferger, Max
2015-10-15 14:27 ` Ian Campbell
2015-10-19 12:09   ` Ferger, Max
2015-10-19 12:44     ` Julien Grall
2015-10-20  8:48       ` Ferger, Max
2015-10-20 10:05         ` Julien Grall
2015-10-20 10:47           ` Julien Grall
2015-10-20 11:41             ` Ferger, Max
2015-10-20 11:23       ` Ferger, Max
2015-10-20 21:44         ` Julien Grall [this message]
2015-10-21 16:05           ` Ferger, Max
2015-10-21 16:23             ` Julien Grall
2015-10-21 17:20               ` Ferger, Max
2015-10-21 18:01                 ` Julien Grall
2015-10-22 15:07                   ` Ferger, Max
2015-10-22 15:29                     ` Julien Grall
2015-10-22  8:48                 ` Ian Campbell

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=5626B5AA.6060304@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=M.Ferger@KOSTAL.COM \
    --cc=ian.campbell@citrix.com \
    --cc=iurii.konovalenko@globallogic.com \
    --cc=oleksandr.tyshchenko@globallogic.com \
    --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 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.