From: Avi Kivity <avi@qumranet.com>
To: david ahern <daahern@cisco.com>
Cc: KVM <kvm-devel@lists.sourceforge.net>
Subject: Re: [ANNOUNCE] kvm-driver-disc-20080318
Date: Wed, 19 Mar 2008 17:43:56 +0200 [thread overview]
Message-ID: <47E134BC.7020409@qumranet.com> (raw)
In-Reply-To: <47E129FB.5010700@cisco.com>
david ahern wrote:
> Avi Kivity wrote:
>
>> It might be difficult for RHEL 4, which is 2.6.5 based IIRC. If the
>> magic required is more that 500 millithaums, then an independent driver
>> would be better.
>>
>
> RHEL4 is based on 2.6.9.
>
> What do you mean by "magic required is more that 500 millithaums"?
>
>
A Thaum is the amount of magic required to conjure one standard white
pigeon.
I meant that the amount of changes needed to port the driver to 2.6.9 is
too large, the script to do automatic backporting might turn out to be
less maintainable than keeping an independent source tree. We're not
far from that point even for 2.6.18; for example running the script
against 2.6.25-current will produce an unbuildable driver.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-19 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 15:42 [ANNOUNCE] kvm-driver-disc-20080318 Avi Kivity
2008-03-18 19:39 ` david ahern
2008-03-18 19:50 ` Anthony Liguori
2008-03-19 12:23 ` Avi Kivity
2008-03-19 14:58 ` david ahern
2008-03-19 15:29 ` Anthony Liguori
2008-03-19 15:53 ` david ahern
2008-03-19 15:43 ` Avi Kivity [this message]
2008-03-19 14:51 ` Alexey Eremenko
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=47E134BC.7020409@qumranet.com \
--to=avi@qumranet.com \
--cc=daahern@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox