Re: [Xen-devel] [PATCH v2] xen: arm64: Add support for Renesas RCar Gen3 H3 Salvator-X platform

[Julien Grall <julien.grall@xxxxxxx>]

Hi Dirk,

On 07/07/16 11:39, Dirk Behme wrote:
> On 06.07.2016 16:21, Julien Grall wrote:
> > On 06/07/16 15:03, Dirk Behme wrote:
> > > On 06.07.2016 15:17, Julien Grall wrote:
> > > > Hi Dirk,
> > > >
> > > > On 06/07/16 07:33, Dirk Behme wrote:
> > > > > Could you share the U-Boot commands how you load and esp. start Xen?
> > > > > For
> > > > > loading you use TFTP? How do you start Xen with U-Boot, then? I
> > > > > think we
> > > > > have to pass the device tree address in x0 and the Linux kernel image
> > > > > address in x2. How do you do this with an U-Boot command?
> > > > U-boot can load Xen from TFTP or from the SD-card. This is the same as
> > > > booting a baremetal kernel with U-boot.
> > > >
> > > > There is a section on the wiki page to explain how to create the
> > > > device-tree node for the boot modules [1] and the allwinner page [2]
> > > > gives a full example how to boot Xen with U-boot via tftp (Note that it
> > > > could easily be adapted to load from the SD-Card).
> > > >
> > > > Regards,
> > > >
> > > > [1]
> > > > http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions#Boot_Modules
> > > >
> > > >
> > > >
> > > >
> > > > [2]
> > > > http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner#Boot_script
> > >
> > > Hmm, sorry, I still seem to miss anything :(
> > >
> > > I've loaded xen/xen with U-Boot to 0x4A000000 and then try to start it
> > > as described in [2] above:
> > >
> > > => bootz 0x4A000000 - 0x48000000
> > > Bad Linux ARM zImage magic!
> > >
> > > I'm not sure why xen/xen is assumed to be a zImage?
> > Oh, sorry I meant to say that bootz should be replaced by booti but
> > forgot to write it down.
>
> Ok, thanks, booti does work [1].
Good to know!

> Most probably just cosmetics, but again our friend image_size:
>
> Image lacks image_size field, assuming 16MiB
>
> Is there any special reason why we don't write the image size to the xen
> header?
>
> Or should we try to fix it? E.g. like the Linux kernel is doing it?
The support of Xen ARM64 was added before the size was extended with the 
size. We did not update the header since then.
I had the same warning a couple of weeks ago and have a patch in my xen 
tree at home. I will try to send it tonight.
Cheers,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel