All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: kvm-devel <kvm-devel@lists.sourceforge.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] kvm-10 release
Date: Sun, 07 Jan 2007 15:17:27 +0200	[thread overview]
Message-ID: <45A0F2E7.4020102@qumranet.com> (raw)

Changes from kvm-9:

- more hypercall work
- cleanup irq handling
- shadow page table caching
- migration fixes
- stabilization fixes

This release is significantly faster than previous releases; upgrading 
is recommended.

http://kvm.sourceforge.net

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: linux-kernel <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [ANNOUNCE] kvm-10 release
Date: Sun, 07 Jan 2007 15:17:27 +0200	[thread overview]
Message-ID: <45A0F2E7.4020102@qumranet.com> (raw)

Changes from kvm-9:

- more hypercall work
- cleanup irq handling
- shadow page table caching
- migration fixes
- stabilization fixes

This release is significantly faster than previous releases; upgrading 
is recommended.

http://kvm.sourceforge.net

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

             reply	other threads:[~2007-01-07 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07 13:17 Avi Kivity [this message]
2007-01-07 13:17 ` [ANNOUNCE] kvm-10 release 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=45A0F2E7.4020102@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@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.