Commit 9b463334 authored by Jeremy Fitzhardinge's avatar Jeremy Fitzhardinge Committed by Ingo Molnar

vmap: cope with vm_unmap_aliases before vmalloc_init()

Xen can end up calling vm_unmap_aliases() before vmalloc_init() has
been called.  In this case its safe to make it a simple no-op.
Signed-off-by: default avatarJeremy Fitzhardinge <>
Cc: Linux Memory Management List <>
Cc: Nick Piggin <>
Signed-off-by: default avatarIngo Molnar <>
parent 4bab0ea1
......@@ -592,6 +592,8 @@ static void free_unmap_vmap_area_addr(unsigned long addr)
static bool vmap_initialized __read_mostly = false;
struct vmap_block_queue {
spinlock_t lock;
struct list_head free;
......@@ -828,6 +830,9 @@ void vm_unmap_aliases(void)
int cpu;
int flush = 0;
if (unlikely(!vmap_initialized))
for_each_possible_cpu(cpu) {
struct vmap_block_queue *vbq = &per_cpu(vmap_block_queue, cpu);
struct vmap_block *vb;
......@@ -942,6 +947,8 @@ void __init vmalloc_init(void)
vbq->nr_dirty = 0;
vmap_initialized = true;
void unmap_kernel_range(unsigned long addr, unsigned long size)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment