From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Carlo Marcelo Arenas Belon
<carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [ANNOUNCE] kvm-56 release
Date: Sun, 16 Dec 2007 13:34:56 +0200 [thread overview]
Message-ID: <47650D60.7040705@qumranet.com> (raw)
In-Reply-To: <20071216085411.GA6045@tapir>
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
prev parent reply other threads:[~2007-12-16 11:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 13:32 [ANNOUNCE] kvm-56 release Avi Kivity
[not found] ` <4761347E.9090806-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-13 14:19 ` Pelle
2007-12-13 14:24 ` Alexey Eremenko
[not found] ` <64F9B87B6B770947A9F8391472E032160C95C606-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-12-13 14:58 ` Pelle
[not found] ` <47613F6B.5030508-5JapdU7xTciEVqv0pETR8A@public.gmane.org>
2007-12-13 14:56 ` Avi Kivity
[not found] ` <4761480C.6020204-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-13 15:22 ` Pelle
[not found] ` <47614E53.2070809-5JapdU7xTciEVqv0pETR8A@public.gmane.org>
2007-12-13 15:29 ` Avi Kivity
[not found] ` <47614FCB.6060705-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-13 15:38 ` Pelle
2007-12-13 14:59 ` Alexey Eremenko
[not found] ` <64F9B87B6B770947A9F8391472E032160C95C607-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-12-13 15:06 ` Avi Kivity
[not found] ` <47614A81.90803-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-14 16:26 ` Carlo Marcelo Arenas Belon
2007-12-14 16:11 ` Carlo Marcelo Arenas Belon
2007-12-13 15:13 ` Farkas Levente
[not found] ` <47614C02.60904-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-12-13 16:42 ` Izik Eidus
[not found] ` <4761610B.1040304-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-13 21:50 ` Farkas Levente
[not found] ` <4761A921.2060701-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-12-16 8:19 ` Izik Eidus
2007-12-13 19:05 ` Theodore Tso
[not found] ` <20071213190545.GC9921-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2007-12-14 14:39 ` Avi Kivity
2007-12-16 8:54 ` Carlo Marcelo Arenas Belon
2007-12-16 11:34 ` 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=47650D60.7040705@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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