Thread (26 messages) flat view 26 messages, 3 authors, 2016-02-19
DORMANTno replies

Revision v1 of 6 in this series.

Revisions (6)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v1 [diff vs current]
  5. v1 [diff vs current]
  6. v1 current

[PATCH v6sub1 00/11] arm64: split linear and kernel mappings

From: catalin.marinas@arm.com (Catalin Marinas)
Date: 2016-02-19 17:43:49

On Fri, Feb 19, 2016 at 06:38:19PM +0100, Ard Biesheuvel wrote:
quoted
I noticed that we still have MODULES_VADDR around and used in couple of
places (printing the kernel memory layout during init, debugfs
kernel_page_tables and KASAN). Shouldn't we use module_alloc_base
instead?
For KASAN, I updated the patches so that the modules are always
allocated in the original module region, to prevent issues with the
zero shadow that backs the vmalloc region.
Ah, I forgot about this.
For the other purposes, it is really a matter of taste. The reserved
region still exists, KASLR or not, so if you omit it, you will have a
hole in the memory map. For the page table dumper, i did not add a
special section for the kernel either.

I'm happy to propose a patch that changes that, once we (you) decide
what you want to see.
Leave it as it is for now.

-- 
Catalin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help