|
@@ -4,7 +4,7 @@
|
|
Guest Loader
|
|
Guest Loader
|
|
------------
|
|
------------
|
|
|
|
|
|
-The guest loader is similar to the `generic-loader` although it is
|
|
|
|
|
|
+The guest loader is similar to the ``generic-loader`` although it is
|
|
aimed at a particular use case of loading hypervisor guests. This is
|
|
aimed at a particular use case of loading hypervisor guests. This is
|
|
useful for debugging hypervisors without having to jump through the
|
|
useful for debugging hypervisors without having to jump through the
|
|
hoops of firmware and boot-loaders.
|
|
hoops of firmware and boot-loaders.
|
|
@@ -27,12 +27,12 @@ multi-boot capability. A typical example would look like:
|
|
In the above example the Xen hypervisor is loaded by the -kernel
|
|
In the above example the Xen hypervisor is loaded by the -kernel
|
|
parameter and passed it's boot arguments via -append. The Dom0 guest
|
|
parameter and passed it's boot arguments via -append. The Dom0 guest
|
|
is loaded into the areas of memory. Each blob will get
|
|
is loaded into the areas of memory. Each blob will get
|
|
-`/chosen/module@<addr>` entry in the FDT to indicate it's location and
|
|
|
|
|
|
+``/chosen/module@<addr>`` entry in the FDT to indicate it's location and
|
|
size. Additional information can be passed with by using additional
|
|
size. Additional information can be passed with by using additional
|
|
arguments.
|
|
arguments.
|
|
|
|
|
|
Currently the only supported machines which use FDT data to boot are
|
|
Currently the only supported machines which use FDT data to boot are
|
|
-the ARM and RiscV `virt` machines.
|
|
|
|
|
|
+the ARM and RiscV ``virt`` machines.
|
|
|
|
|
|
Arguments
|
|
Arguments
|
|
^^^^^^^^^
|
|
^^^^^^^^^
|