Skip to content

x86/mm: unmapping and marking-as-I/O in arch_init_memory()

Jan Beulich xen-devel 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest2 patches 5 repliesIn review
  2. v1 RFC1 patch 1 replySuperseded

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2x86/mkelf32: pad load segment to 2Mb boundaryxen/arch/x86/Makefile xen/arch/x86/boot/mkelf32.c+12 -93 replies
2/2x86/mm: drop unmapping from marking-as-I/O in arch_init_memory()xen/arch/x86/mm.c+9 -162 replies

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchRoger Pau Monné
1/2A-b
2/2A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v2 thread

Cover letter [PATCH v2 0/2] x86/mm: unmapping and marking-as-I/O in arch_init_memory()

What we unmap there are mappings we better wouldn't have established in the first place. Arrange for us to only ever map RAM, and then drop the unmapping code, which was flawed anyway.

Nothing with a similar effect as patch 1 needs doing for xen.efi: Prior to GNU binutils commit a844415db878 ("bfd/PE: correct SizeOfImage calculation") too large a size was calculated. With that change in place, image size is properly rounded up to a multiple of 2Mb.

1: mkelf32: pad load segment to 2Mb boundary
2: mm: drop unmapping from marking-as-I/O in arch_init_memory()

Jan