public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] External module compatibility for hrtimer_expires_remaining
Date: Wed, 04 Feb 2009 19:19:43 +0200	[thread overview]
Message-ID: <4989CE2F.90007@redhat.com> (raw)
In-Reply-To: <4989BF82.6030403@suse.de>

Alexander Graf wrote:
> Avi Kivity wrote:
>   
>> Alexander Graf wrote:
>>     
>>> Alexander Graf wrote:
>>>       
>>>> Due to Marcelo's APIC fix we now depend on hrtimer_expires_remaining,
>>>> which is not available on my 2.6.27 kernel.
>>>>
>>>> This patch adds a backwards compatibility layer for it.
>>>>
>>>> Signed-off-by: Alexander Graf <agraf@suse.de>
>>>>         
>>> I just saw that you did one yourself that doesn't work for me. Is the
>>> #define reversed?
>>>       
>> See also my change to hack-module.awk. Did you 'make sync' again?
>>     
>
> On a freshly git pull'ed checkout with a 2.6.27 host kernel:
>
> /dev/shm/x/kvm-userspace/kernel/x86/lapic.c: In function ‘apic_get_tmcct’:
> /dev/shm/x/kvm-userspace/kernel/x86/lapic.c:570: error: implicit
> declaration of function ‘hrtimer_expires_remaining’
> /dev/shm/x/kvm-userspace/kernel/x86/lapic.c:570: error: incompatible
> types in assignment
>
> I'd say the problem is the
>
> #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,27)
>
> which should be 2.6.28, right?
>   

You're right -- will fix.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2009-02-04 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 20:05 [PATCH] External module compatibility for hrtimer_expires_remaining Alexander Graf
2009-01-22 21:20 ` Alexander Graf
2009-02-04 14:41   ` Avi Kivity
2009-02-04 16:17     ` Alexander Graf
2009-02-04 17:19       ` Avi Kivity [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=4989CE2F.90007@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.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