On Wed, Jul 22, 2009 at 01:18:29PM -0500, Anthony Liguori wrote:
Luiz Capitulino wrote:
In QEMU you mean?
The first commit introducing it seems to be
e22a25c9361c44995c9241c24df0e1e2c47a56c8 , but I have no idea
on how this macro and its code are being used.
No, I was asking when it was introduced in KVM. We have a minimal set
of capabilities that we require. It looks like KVM_CAP_SET_GUEST_DEBUG
arrived shortly after KVM_CAP_DESTROY_MEMORY_REGION which is our current
minimum.
How will this minimum change if we start backporting things like memory aliasing
broken for qemu?