Carlo Marcelo Arenas Belon wrote:
> On Thu, Dec 13, 2007 at 03:32:46PM +0200, Avi Kivity wrote:
>   
>> Notes:
>>       If you use the modules bundled with kvm-56, you can use any version
>> of Linux from 2.6.9 upwards.
>>     
>
> the external module (once patched) will only be able to build against 2.6.17
> upwards because the in-kernel PIC/IOAPIC/LAPIC requires hrtimers and that
> functionality was only made public to external modules during the 
> stabilization
> of 2.6.17 as seen by :
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8d16b76421f0b3216012ee2d7819355e1cb847e5
>
> there are obviously 3 possible fixes :
>
> 1) rewrite the in-kernel PIC/IOAPIC/LAPIC not to use hrtimers (not worthy)
> 2) replicate the functionality needed in the compatibility header or with the
> use of a helper (not that simple)
> 3) disable the functionality and ifdef the code for kernel < 2.6.17
> (preferred)
>
> but before, I would like to ask: is 2.6.9 upwards support really needed?, 

I imagine you're right, since there are few complaints.  Most people 
have migrated to RHEL 5 or its equivalents.

> the
> only reason why I would suspect that 2.6.9 was recommended was because of
> RHEL4

Yes.

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


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to