From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Dom0 kernel for Xen4.6 on R-Car H2 (LAGER) Date: Tue, 20 Oct 2015 22:44:10 +0100 Message-ID: <5626B5AA.6060304@citrix.com> References: <5a0aab3289b446c1877348268f2afc39@DEBEMAIL001.kostal.int> <1444919269.1607.95.camel@citrix.com> <0234f7a69dc647fa80b6d16a8f5a7fc8@DEBEMAIL001.kostal.int> <5624E5A0.4030906@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Ferger, Max" , Ian Campbell , "xen-devel@lists.xen.org" Cc: Oleksandr Tyshchenko , Iurii Konovalenko List-Id: xen-devel@lists.xenproject.org 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