From: Anthony Liguori <aliguori@us.ibm.com>
To: Glauber Costa <glommer@redhat.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] Re: Build currently broken
Date: Wed, 22 Jul 2009 13:30:28 -0500 [thread overview]
Message-ID: <4A675AC4.1000701@us.ibm.com> (raw)
In-Reply-To: <20090722183554.GT4019@poweredge.glommer>
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
next prev parent reply other threads:[~2009-07-22 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 17:15 [Qemu-devel] Build currently broken Luiz Capitulino
2009-07-22 17:58 ` [Qemu-devel] " Anthony Liguori
2009-07-22 18:10 ` Luiz Capitulino
2009-07-22 18:18 ` Anthony Liguori
2009-07-22 18:35 ` Glauber Costa
2009-07-22 18:30 ` Anthony Liguori [this message]
2009-07-22 19:05 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A675AC4.1000701@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=glommer@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).