> Traping the read deals with the first. The second shouldn't be a problem since > we generally only allow kernel info for CAP_ADMIN; if we don't already for LBR > that needs to be fixed separately.
Where is that check? I don't see it. Also remember that precise == 2 can enable LBR implicitly. > That only leaves the third.. can we descern MMIO maps from the kernel page > tables? In theory you could use some bits in the PTE for vmalloc, but it would need quite a few changes. Also there may be corner cases where MMIO is in the direct mapping or in the kernel mapping. -Andi -- a...@linux.intel.com -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
