Nick Piggin wrote: >> Or run purge_vma_area_lazy from keventd? > > Right. But that's only needed if we want to vmap from irq context too > (otherwise we can just do the purge check at vmap time). > > Is there any good reason to be able to vmap or vunmap from interrupt > time, though? It would be good to have vunmap work in an interrupt context like other free operations. One may hold spinlocks while freeing structure. vmap from interrupt context would be useful f.e. for general fallback in the page allocator to virtually mapped memory if no linear physical memory is available (virtualizable compound pages). Without a vmap that can be run in an interrupt context we cannot support GFP_ATOMIC allocs there. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
