xen.txt 2.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061
  1. * Xen hypervisor device tree bindings
  2. Xen ARM virtual platforms shall have a top-level "hypervisor" node with
  3. the following properties:
  4. - compatible:
  5. compatible = "xen,xen-<version>", "xen,xen";
  6. where <version> is the version of the Xen ABI of the platform.
  7. - reg: specifies the base physical address and size of a region in
  8. memory where the grant table should be mapped to, using an
  9. HYPERVISOR_memory_op hypercall. The memory region is large enough to map
  10. the whole grant table (it is larger or equal to gnttab_max_grant_frames()).
  11. This property is unnecessary when booting Dom0 using ACPI.
  12. - interrupts: the interrupt used by Xen to inject event notifications.
  13. A GIC node is also required.
  14. This property is unnecessary when booting Dom0 using ACPI.
  15. To support UEFI on Xen ARM virtual platforms, Xen populates the FDT "uefi" node
  16. under /hypervisor with following parameters:
  17. ________________________________________________________________________________
  18. Name | Size | Description
  19. ================================================================================
  20. xen,uefi-system-table | 64-bit | Guest physical address of the UEFI System
  21. | | Table.
  22. --------------------------------------------------------------------------------
  23. xen,uefi-mmap-start | 64-bit | Guest physical address of the UEFI memory
  24. | | map.
  25. --------------------------------------------------------------------------------
  26. xen,uefi-mmap-size | 32-bit | Size in bytes of the UEFI memory map
  27. | | pointed to in previous entry.
  28. --------------------------------------------------------------------------------
  29. xen,uefi-mmap-desc-size | 32-bit | Size in bytes of each entry in the UEFI
  30. | | memory map.
  31. --------------------------------------------------------------------------------
  32. xen,uefi-mmap-desc-ver | 32-bit | Version of the mmap descriptor format.
  33. --------------------------------------------------------------------------------
  34. Example (assuming #address-cells = <2> and #size-cells = <2>):
  35. hypervisor {
  36. compatible = "xen,xen-4.3", "xen,xen";
  37. reg = <0 0xb0000000 0 0x20000>;
  38. interrupts = <1 15 0xf08>;
  39. uefi {
  40. xen,uefi-system-table = <0xXXXXXXXX>;
  41. xen,uefi-mmap-start = <0xXXXXXXXX>;
  42. xen,uefi-mmap-size = <0xXXXXXXXX>;
  43. xen,uefi-mmap-desc-size = <0xXXXXXXXX>;
  44. xen,uefi-mmap-desc-ver = <0xXXXXXXXX>;
  45. };
  46. };
  47. The format and meaning of the "xen,uefi-*" parameters are similar to those in
  48. Documentation/arm/uefi.txt, which are provided by the regular UEFI stub. However
  49. they differ because they are provided by the Xen hypervisor, together with a set
  50. of UEFI runtime services implemented via hypercalls, see
  51. http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,platform.h.html.