All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: kvm <kvm@vger.kernel.org>
Subject: [ANNOUNCE] kvm-kmod-2.6.33-rc6
Date: Sat, 30 Jan 2010 17:40:12 +0100	[thread overview]
Message-ID: <4B6460EC.3020801@web.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

The update queue for 2.6.33 is empty, so it's time to role out the first
 kvm-kmod -rc package for this upcoming kernel. Find the list of KVM
enhancements below, but also the two feature reductions of kvm-kmod that
this step required. However, they are not expected to cause any pain for
 the vast majority of users.

The download is available at

https://sourceforge.net/projects/kvm/files/kvm-kmod/2.6.33-rc6/kvm-kmod-2.6.33-rc6.tar.bz2/download

Major KVM changes since kvm-kmod-2.6.32.7:
 - improved kernel context switching speed
 - better interoperation with other users of virtualization extensions
 - improved irq scaling
 - nested SVM improvements
 - improved cpufreq integration
 - spin loop detection on newer hardware
 - adjustable paravirtual clock
 - Xen PV-on-HVM guest support
 - paravitual MMU is no longer advertised
 - further improvements of x86 emulator

kvm-kmod changes:
 - Drop workaround for !CONFIG_PREEMPT_NOTIFIERS for >= 2.6.33
   (due to technical conflict, but upcoming distro kernels are likely
   shipping with CONFIG_KVM=m which enables them)
 - Disable ioeventfd and irqfd for host kernels < 2.6.33
   (no users expected + there is an unfixable race in older kernels)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

                 reply	other threads:[~2010-01-30 16:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4B6460EC.3020801@web.de \
    --to=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.