[v3,0/3] x86/pvh: Support relocating dom0 kernel

Message

Jason Andryuk March 19, 2024, 8:58 p.m. UTC

Xen tries to load a PVH dom0 kernel at the fixed guest physical address
from the elf headers.  For Linux, this defaults to 0x1000000 (16MB), but
it can be configured.

Unfortunately there exist firmwares that have reserved regions at this
address, so Xen fails to load the dom0 kernel since it's not RAM.

The other issue is that the Linux PVH entry point is not
position-independent.  It expects to run at the compiled
CONFIG_PHYSICAL_ADDRESS.

This patch set expands the PVH dom0 builder to try to relocate the
kernel if needed and possible.  XEN_ELFNOTE_PHYS32_RELOC is added for
kernels to indicate they are relocatable and their acceptable address
range and alignment.

The first patch reverts "xen/x86: bzImage parse kernel_alignment" since
the alignment will be specified by the ELF note.

The second patch expands ELF note printing beyond just printing
integers and strings.

The third patch expands the pvh dom0 kernel placement code.

I'll post an additional patch showing the Linux changes to make PVH
relocatable.

Jason Andryuk (3):
  Revert "xen/x86: bzImage parse kernel_alignment"
  libelf: Expand ELF note printing
  x86/PVH: Support relocatable dom0 kernels

 xen/arch/x86/bzimage.c             |  4 +-
 xen/arch/x86/hvm/dom0_build.c      | 98 +++++++++++++++++++++++++++++-
 xen/arch/x86/include/asm/bzimage.h |  2 +-
 xen/arch/x86/pv/dom0_build.c       |  2 +-
 xen/common/libelf/libelf-dominfo.c | 83 ++++++++++++++++++-------
 xen/include/public/elfnote.h       | 18 +++++-
 xen/include/xen/libelf.h           |  4 ++
 7 files changed, 181 insertions(+), 30 deletions(-)