[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH V2 00/12] arm: support for initial modules (e.g. dom0) and DTB supplied in RAM

  • To: xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  • Date: Tue, 13 Nov 2012 16:22:59 +0000
  • Delivery-date: Tue, 13 Nov 2012 16:23:10 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

The following series implements support for initial images and DTB in
RAM, as opposed to in flash (dom0 kernel) or compiled into the
hypervisor (DTB). It arranges to not clobber these with either the h/v
text on relocation or with the heaps and frees them as appropriate.

Most of this is independent of the specific bootloader protocol which is
used to tell Xen where these modules actually are, but I have included a
simple PoC bootloader protocol based around device tree which is similar
to the protocol used by Linux to find its initrd
(where /chosen/linux,initrd-{start,end} indicate the physical address).

The PoC protocol is documented in docs/misc/arm/device-tree/booting.txt
which is added by this series.

I will post a patch against the boot-wrapper which implements the
"bootloader" side of this protocol shortly. With that you can boot using
the semi-hosting feature of the model (paths are host paths) like so:
        $MODEL linux-system-semi.axf -C cluster.cpu0.semihosting-cmd_line=\
                '--kernel xen-arm.bin \
                 --module zImage earlyprintk=xenboot console=ttyAMA1 
root=/dev/mmcblk0 ro \
                 --dtb vexpress-v2p-aem-v7a-xen.dtb -- dom0_mem=256M'

Where xen-arm.bin, zImage and vexpress-v2p-aem-v7a-xen.dtb are all files
in your $CWD.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.