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

[Xen-devel] [PATCH 00/08 V2] 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: Mon, 3 Dec 2012 17:10:11 +0000
  • Delivery-date: Mon, 03 Dec 2012 17:10:49 +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.

Some of the smaller patches went in already, but most of the meat
remains.

The major change this time is that the protocol now uses a reg property
for the address and size, e.g. something like this:
        /chosen/modules@1 {
                bootargs = "root=/dev/mmcblk0 ro debug"
                reg = <0x200000 0x2000>
        }

I have pushed an updated boot-wrapper to:
git://xenbits.xen.org/people/ianc/boot-wrapper.git

Ian.


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


 


Rackspace

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