public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [ANNOUNCE] kvm-37 release
Date: Sun, 09 Sep 2007 14:05:13 +0300	[thread overview]
Message-ID: <46E3D369.8000401@qumranet.com> (raw)

This release merges the pic/lapic/ioapic into mainline.  While some 
known issues exist, we're now at the point where it's better to get some 
wider exposure rather than keep it alone on a branch.

Some regressions are expected; please report them as they appear.  A new 
qmeu option -no-kvm-irqchip is available to disable the new functionality.

While many people are listed in the credits for this effort, I'd like to 
thank Eddie and Qing for persevering and doing the hard work of actually 
getting it in a form suitable for inclusion and fixing the bugs.  This 
release is mostly their work.

Changes since kvm-36:
- in-kernel lapic, ioapic, and pic (Eddie Dong, Qing He, Sheng Yang, 
Gregory Haskins, Dor Laor, me)
- split segment reload (vmx microoptimization) (Laurent Vivier)
- fix vga redraw regression (Izik Eidus)
- fix testsuite compilation with older assemblers (H. Peter Anvin)

Notes:
    If you use the modules bundled with kvm-37, you can use any version
of Linux from 2.6.9 upwards.
    If you use the modules bundled with Linux 2.6.20, you need to use
kvm-12.
    If you use the modules bundled with Linux 2.6.21, you need to use
kvm-17.
    Modules from Linux 2.6.22 and up will work with any kvm version from
kvm-22.  Some features may only be available in newer releases.
    For best performance, use Linux 2.6.23-rc2 or later as the host.

http://kvm.qumranet.com



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

             reply	other threads:[~2007-09-09 11:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-09 11:05 Avi Kivity [this message]
2007-09-09 14:26 ` [ANNOUNCE] kvm-37 release Jindrich Makovicka
     [not found] ` <46E3D369.8000401-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-09 15:36   ` kvm-37 problem w/ 64-bit division in lapic.c Jindrich Makovicka
2007-09-09 15:45     ` Avi Kivity
2007-09-10  9:20     ` Dong, Eddie
     [not found]       ` <10EA09EFD8728347A513008B6B0DA77A02108583-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-10  9:49         ` Jindrich Makovicka
     [not found]           ` <5f0e26840709100249y239692c2gcdd3938fc6b23b6c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-10 16:26             ` Jindrich Makovicka
2007-09-12  8:05               ` Avi Kivity
     [not found]                 ` <46E79DCA.70101-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-12  9:43                   ` Dong, Eddie
     [not found]                     ` <10EA09EFD8728347A513008B6B0DA77A0210915A-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-12  9:56                       ` Avi Kivity

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=46E3D369.8000401@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox