public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>, Marcelo Tosatti <marcelo@redhat.com>
Subject: Re: Jan Kiszka to maintain kvm-kmod
Date: Mon, 26 Oct 2009 18:51:22 +0100	[thread overview]
Message-ID: <4AE5E19A.6010202@siemens.com> (raw)
In-Reply-To: <4AE565A9.4000907@redhat.com>

Avi Kivity wrote:
> I am pleased to announce that Jan Kiszka has agreed to maintain 
> kvm-kmod.git, the backporting kit that allows running modern kvm code on 
> older kernels.  Jan will release kvm-kmod-2.6.x.y packages and 
> kvm-kmod-2.6.x-rcy packages, while Marcelo and I will (with Jan's help) 
> release kvm-kmod-devel-xx.  Many thanks to Jan for taking on this task.

Thanks for giving me the chance to screw even more things up. :)

Thanks also go to Siemens Corporate Technology and Siemens Enterprise
Communications for sponsoring my work on kvm-kmod.

> As there are now many different sources of kvm kernel modules to choose 
> from, I wrote up a page that describes the various releases and what 
> they are suited for.  This can be found in 
> http://www.linux-kvm.org/page/Getting_the_kvm_kernel_modules.

And besides those releases, I will try to keep the kvm-kmod.git in sync
with latest kvm.git so that developers can test most bleeding-edge kvm
on not that much bleeding host kernels (I'm one of those).

At this chance I would like to underline that the quality of kvm-kmod
support of course continues to depend on patch contributions. So if you
are posting a new kvm feature that may require compat wrapping or you
discover some breakage, please consider posting a corresponding update
of kvm-kmod as well. TiA!

To help detecting breakages, I've set up a builtbot [1] that checks
kvm-mod against its officially supported kvm version as well as the next
branch in kvm.git (the former on commits, the latter on a nightly
basis). That forecast already promises the next rain [2] - time to go
home...

Jan

[1]http://buildbot.kiszka.org/kvm-kmod/
[2]http://buildbot.kiszka.org/kvm-kmod/builders/latest-kvm/builds/11/steps/compile/logs/stdio

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-10-26 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  9:02 Jan Kiszka to maintain kvm-kmod Avi Kivity
2009-10-26 17:51 ` Jan Kiszka [this message]
2009-10-27 10:43   ` Avi Kivity
2009-10-27 11:20     ` Jan Kiszka

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=4AE5E19A.6010202@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=marcelo@redhat.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