> Is remap_page_range working properly? Probably > But the code in remap_pte_range() seems to behave exactly in the opposite > way; as far as I can see, it sets to null every page, _except_ "references > to nonexistent pages"! Here are the relevant lines of code taken from > kernel 2.0.32 (the file is mm/memory.c): You can only remap reserved or I/O space Read drivers/sound a bit - it has code that allocates, reserves and remaps memory - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
