From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH] kvm-userspace: fix compilation breakage when in-kernel pit is not detected
Date: Fri, 11 Apr 2008 09:55:33 -0500 [thread overview]
Message-ID: <47FF7BE5.3080000@codemonkey.ws> (raw)
In-Reply-To: <47FF53F1.4020606@qumranet.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
>> Joerg Roedel wrote:
>>> The compilation of kvm-userspace part fails if the in-kernel pit is not
>>> detected in <linux/kvm.h> with the following error message:
>>>
>>> pc.o: In function `pc_init1':
>>> /home/jroedel/src/kvm/kvm-userspace/qemu/hw/pc.c:987: undefined
>>> reference to `kvm_pit_init'
>>> collect2: ld returned 1 exit status
>>>
>>> This patch fixes this little issue.
>>>
>>
>> A better solution is to wrap qemu_kvm_put_in_kernel in an #ifdef
>> KVM_CAP_PIT so that if it isn't defined, it always returns 0. gcc
>> will then do the right thing.
>>
>
> I would like to move qemu from depending on linux/kvm.h directly.
> However, there is a lot of work needed to get that (including some
> pointless stuff like defining libkvm structures to take the place of
> kvm.h structures) so perhaps it is not a realistic goal.
My real point was that the #ifdef should be in the definition of
qemu_kvm_put_in_kernel() as opposed to in C code. If we use #ifdef
USE_KVM_PIT instead of #ifdef KVM_CAP_PIT that's fine by me.
Regards,
Anthony Liguori
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
prev parent reply other threads:[~2008-04-11 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 12:33 [PATCH] kvm-userspace: fix compilation breakage when in-kernel pit is not detected Joerg Roedel
2008-04-10 23:17 ` Avi Kivity
2008-04-11 4:25 ` Anthony Liguori
2008-04-11 12:05 ` Avi Kivity
2008-04-11 14:55 ` Anthony Liguori [this message]
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=47FF7BE5.3080000@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.