hm. Why dont we instead add the size of the hole to the __VMALLOC_RESERVE value instead? There's nothing inherently bad about using vmalloc=16m. The VM area hole is really a kernel-internal abstraction that should not be visible in the usage of the parameter.