public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Tom Shoes <shoestom@gmail.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: Looking at using KVM for embedded product
Date: Wed, 23 Jun 2010 17:02:18 +0200	[thread overview]
Message-ID: <4C2221FA.9080008@siemens.com> (raw)
In-Reply-To: <AANLkTinr-7ewsnwItR-EfdZ5-AtKkSUjpW4DqB5Jo7U5@mail.gmail.com>

[ please use reply-all when posting to mailing lists ]

Tom Shoes wrote:
> On Wed, Jun 23, 2010 at 3:16 AM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> 
> Thanks Jan for the response.
> 
>> Why 2.6.26, specifically if you seem to have no customized bits?
>> Starting with a pre-historic kernel for a new project is hardly ever a
>> good choice.
> 
>   We had picked up 2.6.26 1 1/2 years back and now there is requirement
> to add virtualization. Many of the other bits has been ported to this kernel
> and 3/4th tested. So moving to newer kernel will be difficult unless there
> is a pressing requirement and this might be from the answer from you
> and Avi.

The effort you may save by sticking with 2.6.26 can quickly be consumed
by troubles and limitations you may face with this old kernel. Better
make sure your local bits are clean and easily portable to recent
kernels version - or even push them upstream. And if you already have a
test suite for your specific scenarios, switching the target shouldn't
be that problematic.

> 
>>>          b.  Will latest KVM code from linux-kvm.org run on Linux kernel 2.6.26?
>> kvm-kmod builds down to 2.6.24, but it is likely only tested down to
>> 2.6.27. And you will miss quite a few relevant performance optimization
>> due to limitations of 2.6.26.
>>
> 
> Do you mean the the KVM community test build every KVM releases down to
> 2.6.24

Speaking of kvm-kmod: http://buildbot.kiszka.org/kvm-kmod/waterfall

> and do testing (may be a cursory one) of KVM functionality down to
> 2.6.27?

Testing of kvm-kmod is a bit less ambitious. This compat package is not
that broadly used compared to the KVM modules that ship with standard or
distribution kernels. There are tests performed against 2.6.27 and
2.6.32 hosts ATM, but anything else depends on community feedback.
Still, we didn't face much kvm-kmod-specific issues in the recent past,
specifically after its stabilization phases.

However, if you decide to upgrade your kernel anyway, I would suggest to
go with the included KVM support first, only pick kvm-kmod if there is a
good reason.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2010-06-23 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23  1:22 Looking at using KVM for embedded product Tom Shoes
2010-06-23  9:36 ` Avi Kivity
     [not found]   ` <AANLkTim56lf5-zCpejM1qzWojp7g__Plzv8-FSzJFuwE@mail.gmail.com>
2010-06-23 14:33     ` Avi Kivity
2010-06-23 14:57       ` Anjali Kulkarni
2010-06-23 15:00         ` Question about mmap from user space and accessing emulated device bar0 contents Anjali Kulkarni
2010-06-24 12:21       ` Looking at using KVM for embedded product Tom Shoes
2010-06-24 12:31         ` Avi Kivity
2010-06-23 10:16 ` Jan Kiszka
     [not found]   ` <AANLkTinr-7ewsnwItR-EfdZ5-AtKkSUjpW4DqB5Jo7U5@mail.gmail.com>
2010-06-23 15:02     ` Jan Kiszka [this message]
2010-06-24 12:25       ` Tom Shoes
2010-06-23 13:45 ` john cooper

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=4C2221FA.9080008@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=shoestom@gmail.com \
    /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