Re: [Xen-devel] Running XEN on imx8mq

[Julien Grall <julien.grall@xxxxxxx>]

Hello,

On 18/03/2019 10:41, Amit Tomer wrote:
> Hello,
>
> > The tree you are using is dirty. What did you change?
> Just added the imx8mq specific debug so that we can see early prints from XEN,
> > [..]
> >
> > > (XEN) GICv3: CPU3: Found redistributor in region 0 @000000004007a000
> > > (XEN) Adding cpu 3 to runqueue 0
> > > (XEN) CPU 3 booted.
> > > (XEN) Brought up 4 CPUs
> > > (XEN) P2M: 40-bit IPA with 40-bit PA and 8-bit VMID
> > > (XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
> > > (XEN) I/O virtualisation disabled
> > > (XEN) build-id: d884da2ad279978f5b120cd02aca4034d898f133
> > > (XEN) alternatives: Patching with alt table 00000000002abbf8 -> 00000000002ac240
> > > (XEN) *** LOADING DOMAIN 0 ***
> > > (XEN) Loading Domd0 kernel from boot module @ 0000000040480000
> > > (XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
> > > (XEN) BANK[0] 0x00000060000000-0x000000a0000000 (1024MB)
> > > (XEN) Grant table range: 0x00000042000000-0x00000042040000
> > > (XEN) Allocating PPI 16 for event channel interrupt
> > > (XEN) Loading zImage from 0000000040480000 to 0000000060080000-0000000061880000
> > > (XEN) dom0 IPA 0x0000000060080000
> > > (XEN) P2M @ 0000000801bff4a0 mfn:0xbffcc
> > > (XEN) Using concatenated root table 0
> > > (XEN) 1ST[0x1] = 0x02c00000400006fd
> > > (XEN) ****************************************
> > > (XEN) Panic on CPU 0:
> > > (XEN) Unable to copy the kernel in the hwdom memory
> > > (XEN) ****************************************
> > This looks like the same problem on encounter on the RCar. I.e the
> > reserved-memory regions are not carved from xenheap pool.
> This is the first thing we tried (removing reserved node from DTS file) but
> it didn't work :(
It will be difficult to help without any log. You probably want to try with 
Stefano series instead. However ...
> Just wondering here, if it has some thing to do with following commit ?
... the tree you point below seems to contains a lot of patches for IMX8 support 
in Xen. So this may or may not be your issue. I am afraid I can't provide help 
on that tree.
Cheers,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel