public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: david ahern <daahern@cisco.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: KVM <kvm-devel@lists.sourceforge.net>, Avi Kivity <avi@qumranet.com>
Subject: Re: [ANNOUNCE] kvm-driver-disc-20080318
Date: Wed, 19 Mar 2008 09:53:07 -0600	[thread overview]
Message-ID: <47E136E3.5000807@cisco.com> (raw)
In-Reply-To: <47E13141.8090403@us.ibm.com>

I cringed a bit when you suggested the awk script route. It's quite likely that
drivers for older distributions have to be manually updated as needed. I'll post
my RHEL4 version in the next couple of days for comments.

thanks,
david


Anthony Liguori wrote:
> 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"?
>>   
> 
> I believe that was a joke :-)
> 
> Right now, we use an awk script to automatically insert a bunch of
> #ifdef COMPAT_xxx into the virtio drivers.  Combined with a special
> include header, this automatically creates a new source tree from the
> upstream bits that can be compiled on many different kernel versions. 
> Right now we support roughly 2.6.18-2.6.25.
> 
> The question is how far can we push this before it gets ridiculous.  I'd
> like to try going back to 2.6.9.  Posting what you have now would be
> helpful.  If it gets too difficult, we may just have to have independent
> source trees for things like RHEL4.
> 
> Regards,
> 
> Anthony Liguori
> 
>> david
>>
>> -------------------------------------------------------------------------
>> 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/
>> _______________________________________________
>> kvm-devel mailing list
>> kvm-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>>   
> 
> 

-------------------------------------------------------------------------
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/

  reply	other threads:[~2008-03-19 15:53 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 [this message]
2008-03-19 15:43         ` Avi Kivity
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=47E136E3.5000807@cisco.com \
    --to=daahern@cisco.com \
    --cc=aliguori@us.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox