From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: Testing xen-arm on Arndale Date: Fri, 29 Mar 2013 12:50:01 +0000 Message-ID: References: <5151C711.5090604@citrix.com> <5151F707.8080704@citrix.com> <51558C47.7000008@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51558C47.7000008@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Julien Grall Cc: Anthony Perard , Xen Devel , Sengul Thomas , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Fri, 29 Mar 2013, Julien Grall wrote: > On 03/29/2013 06:57 AM, Sengul Thomas wrote: > > >> Julien, > >> do you know whether they need to use the Arndale Linux tree you posted > >> on the wiki or if a vanilla Linux kernel should be used as DomU kernel? > >> That's something worth writing down in the wiki page to avoid > >> confusion. > >> > > > > Oops, my bad. vanilla Linux kernel 3.8.4 still has the same problem. > > I did not configure the processor type to Exynos (it was VE) when > > compiling the kernel. > > Linux kernel 3.8.4 still has the same problem and I'm digging into it. > > > > If we see the log below, in this time, translation fault happen at level 2. > > I'm just guessing that page table at hypervisor is not properly set. > > > > (XEN) Guest data abort: Translation fault at level 2 > > (XEN) gva=10000000 > > (XEN) gpa=0000000010000000 > > (XEN) size=2 sign=0 write=0 reg=6 > > (XEN) eat=0 cm=0 s1ptw=0 dfsc=6 > > (XEN) dom3 IPA 0x0000000010000000 > > (XEN) P2M @ 02ff6400 mfn:0xbfb20 > > (XEN) 1ST[0x0] = 0x00000000bfb236ff > > (XEN) 2ND[0x80] = 0x0000000000000000 > > (XEN) ----[ Xen-4.3-unstable arm32 debug=y Tainted: C ]---- > > (XEN) CPU: 0 > > (XEN) PC: 803c2f6c > > > The xenvm-4.2.dts only works with Versatile Expresss, because the gic is not > mapped to the right address. Of course we'll have to fix this at some point, because xenvm is supposed to be a generic VM device tree interface. One day it will probably be generated automatically by the Xen tools.