qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: Build currently broken


From: Anthony Liguori
Subject: [Qemu-devel] Re: Build currently broken
Date: Wed, 22 Jul 2009 13:30:28 -0500
User-agent: Thunderbird 2.0.0.21 (X11/20090320)

Glauber Costa wrote:
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?

Good question. I don't know. I really hate to have all of these #ifdef KVM_CAPs all over the place though.

Maybe we should re-examine pulling in kvm header files.

--
Regards,

Anthony Liguori





reply via email to

[Prev in Thread] Current Thread [Next in Thread]