That's a possibility. They are also pieces in the perf tool itself.If the current MMAP2 is not a complete solution for what you (Google)
need, should support be reverted before 3.12 is released? No sense in
making this part of the forever API if more work is needed on it.
Instead of a full revert we could just turn off the ABI portion minimally
and not recognize it for now. Assuming a more complete solution is in the
works for v3.13.
We could certainly make the attr->mmap2 bit disappear.
I think it boils down to how can we uniquely identify virtual
mapping to the same physical data either via shmat(), files, VM_CLONE.
We had all covered but the last case with the ino approach. We don't have
a solution for VM_CLONE yet.