Charlie Jacobsen authored Feb 02, 2016 and Vikram Narayanan committed Oct 26, 2016

We were doing this before (memory for module bits is vmalloc'd),
but we used a capability per page. This leads to a handful of
cptr's we have to keep track of, rather than just a couple.
Moreover, when I tune page allocation inside the LCD, I may
have to vmalloc memory (if the required chunks are big
enough).

So, one vmalloc allocation should be represented with a
single capability. (We sacrifice some access control granularity.)