From: Anthony Liguori <anthony@codemonkey.ws>
To: Pekka Enberg <penberg@kernel.org>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Avi Kivity <avi@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Prasad Joshi <prasadjoshi124@gmail.com>,
Sasha Levin <levinsasha928@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Asias He <asias.hejun@gmail.com>
Subject: Re: [ANNOUNCE] Native Linux KVM tool v2
Date: Wed, 15 Jun 2011 16:41:50 -0500 [thread overview]
Message-ID: <4DF9271E.2060701@codemonkey.ws> (raw)
In-Reply-To: <1308153214.7566.6.camel@jaguar>
On 06/15/2011 10:53 AM, Pekka Enberg wrote:
> Hi all,
>
> We’re proud to announce the second version of the Native Linux KVM tool! We’re
> now officially aiming for merging to mainline in 3.1.
>
> Highlights:
>
> - Experimental GUI support using SDL and VNC
>
> - SMP support. tools/kvm/ now has a highly scalable, largely lockless driver
> interface and the individual drivers are using finegrained locks.
>
> - TAP-based virtio networking
>
> - Fast QCOW2 image read-write support beating Qemu in fio benchmarks. See the
> following URL for test result details: https://gist.github.com/1026888
What was the commit hash for the QEMU you tested?
The following caused a major regression in qcow2:
commit a16c53b101a9897b0b2be96a1bb3bde7c04380f2
Author: Anthony Liguori <aliguori@us.ibm.com>
Date: Mon Jun 6 08:25:06 2011 -0500
Fix regression introduced by -machine accel=
Commit 85097db6 changed the timing when kvm_allowed is set until after
kvm is initialized. During initialization, the ioeventfd
initialization cod
checks kvm_enabled() and after this change, ioeventfd is
effectively disable
If it's not in your tree, it would be useful to rerun the test with the
latest git.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-06-15 21:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 15:53 [ANNOUNCE] Native Linux KVM tool v2 Pekka Enberg
2011-06-15 16:30 ` Avi Kivity
2011-06-15 17:10 ` Pekka Enberg
2011-06-15 20:13 ` Prasad Joshi
2011-06-15 20:23 ` Sasha Levin
2011-06-15 20:49 ` Prasad Joshi
2011-06-15 21:53 ` Anthony Liguori
2011-06-15 22:04 ` Anthony Liguori
2011-06-15 22:07 ` Alexander Graf
2011-06-15 22:20 ` Anthony Liguori
2011-06-15 22:44 ` Anthony Liguori
2011-06-16 5:41 ` Pekka Enberg
2011-06-16 6:21 ` Pekka Enberg
2011-06-16 9:24 ` Christoph Hellwig
2011-06-16 9:34 ` Pekka Enberg
2011-06-16 9:48 ` Christoph Hellwig
2011-06-16 9:57 ` Ingo Molnar
2011-06-16 9:57 ` Pekka Enberg
2011-06-16 10:02 ` Christoph Hellwig
2011-06-16 11:22 ` Ingo Molnar
2011-06-16 11:25 ` Christoph Hellwig
2011-06-16 11:40 ` Ingo Molnar
2011-06-16 11:51 ` Christoph Hellwig
2011-06-17 7:21 ` Jeff Garzik
2011-06-16 5:45 ` Pekka Enberg
2011-06-16 7:24 ` Ingo Molnar
2011-06-16 7:33 ` Pekka Enberg
2011-06-16 8:07 ` Ingo Molnar
2011-06-16 9:09 ` Stefan Hajnoczi
2011-06-16 5:29 ` Stefan Hajnoczi
2011-06-16 5:42 ` Pekka Enberg
2011-06-15 21:41 ` Anthony Liguori [this message]
2011-06-16 14:28 ` Michael S. Tsirkin
2011-06-16 15:01 ` Asias He
2011-06-19 8:15 ` Michael S. Tsirkin
2011-06-16 14:48 ` Pekka Enberg
2011-06-16 22:50 ` Anthony Liguori
2011-06-17 1:03 ` Sasha Levin
2011-06-17 5:00 ` Stefan Hajnoczi
2011-06-17 13:41 ` Sasha Levin
2011-06-17 13:45 ` Anthony Liguori
2011-06-17 5:11 ` Stefan Hajnoczi
2011-06-17 7:31 ` justin
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=4DF9271E.2060701@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=akpm@linux-foundation.org \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).