Glauber Costa wrote:
I'm currently not aware of a practical use case where this bites, but if
the guest maps some memory from A to B, it may expect to find the
content of A under B as well. That is not the case so far as B remains B
from KVM's POV. At the same time, all QEMU memory access functions see B
as A (that caused trouble for debugging and memory sniffing monitor
services).
It looks like KVM aliasing support, that (up to now), seemed completely
orthogonal.
I'm looking at ways to integrate aliasing now, so if you can provide me with
some use
cases of what you described above, (that seem to have happened in your
debugging patches),
it would surely help.
Aliasing/remapping can now be implemented using memory slots. Simply
map the same hva to different gpas.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
