What's the rational behind /dev/mem not being able to map unreserved RAM?
It can't be for protecting the system, because if you have access to
reserved RAM (kernel text) then you can modify the remap_pte_range to
allow for mapping of ram.
I have a user program for debugging kernel modules and the like, and it
uses /dev/mem to map ram and prints it out. But unless I take out the
check in remap_pte_range, I can't see allocated pages.
I just want to know the rational behind this.
Thanks,
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/