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

Re: [Xen-devel] [PATCH v2] tools: implement initial ramdisk support for ARM.



Ian Campbell writes ("[PATCH v2] tools: implement initial ramdisk support for 
ARM."):
> The ramdisk is passed to the kernel as a property in the chosen node
> of the device tree. This is somewhat tricky since in order to place
> the ramdisk and dtb in ram we first need to know the size of the
> dtb. So we initially create a DTB with placeholders for the ramdisk
> and finalise the value (which doesn't change the size) once we know
> where everything is.

Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

I'll leave you to push it (perhaps after giving time for others to
comment on v2).

> I'm considering proposing this for backport to 4.4 since lack of
> initrd support is at the very least rather inconvenient for many use
> cases.

I think this is a viable backport candidate.  Can you let me know when
it's in-tree and I'll add it to my list.

> Also, should we consider (separate from this change) making libxc not
> decompress the consider ramdisk by default? These days Linux at least can do
> the decompress itself and supports more algorithmns, like xz.

DYK whether Linux has ever not been able to decompress itself - and if
so when did this change ?  It would be annoying to break some old
installations.

Looking at the code, it might be a good idea to at least pass unknown
compression formats on to the kernel, rather than failing as we do
now.

Thanks,
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®.