search for: xc_dom_armzimageloader

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

Hi, I was wondering if there is any documentation on how to write a bare metal application for Xen. I don''t need to parse the device tree and such yet, a simple booting "Hello World" would be fine :-) We wrote one and when trying to boot we get ( this was an uncompressed binary, no image): libxl: notice: libxl_numa.c:451:libxl__get_numa_candidate: NUMA placement failed,

Biggest change is to switch the new DTB node to /xen-core-devices instead of /xen at Stefano''s request. I also dropped the few patches title HACK etc which weren''t supposed to be there and fixed up some bits and pieces which folks commented on. George, WRT the freeze I think this is functionality which we cannot ship Xen 4.4 without. The impact is entirely constrained to the

...hich includes lists of packages to install etc. > I also found that xc_dom_elfloader.c’s function, xc_dom_guest_type(), > did not know about the EM_ARM machine type. You shouldn't be hitting the elf loader paths, you should instead use the zImage version of the kernel which will hit the xc_dom_armzimageloader.c code paths. We did at one point in the very early days of the port support loading ELF files via a quick hack of a tool ("xcbuild") but that has been superceded by the proper toolstack support and the use of zImage. > Am I using the wrong repo for development of the tools for ARM?...

Linux 3.11 added respective support, so I think we should follow suit. 1: xen: add LZ4 decompression support 2: libxc: add LZ4 decompression support Signed-off-by: Jan Beulich <jbeulich@suse.com>