From: Avi Kivity <avi@redhat.com>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM Test report, kernel 647e9e... qemu 7811d4...
Date: Wed, 24 Mar 2010 17:17:34 +0200 [thread overview]
Message-ID: <4BAA2D0E.1010606@redhat.com> (raw)
In-Reply-To: <EB8593BCECAB3D40A8248BE0B6400A3846385D9D@shzsmsx502.ccr.corp.intel.com>
On 03/08/2010 08:40 AM, Hao, Xudong wrote:
> Hi, all,
> This is KVM biweekly test result against kvm.git: 647e9ec3b543ea04d49a7323dfe0070682ed8465 and qemu-kvm.git: 7811d4e8ec057d25db68f900be1f09a142faca49.
>
> In the last month, KVM testing was blocked by one qemu-img issue and two qemu build issues. Now the qemu build issue and qemu-img bug all get fixed.
>
> 2. ltp diotest running time is 2.54 times than before
> https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831
>
Can you check the performance of this with cache=writeback?
The common on the report referring to cache=writethrough is incorrect (I
think?)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-24 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 6:40 KVM Test report, kernel 647e9e... qemu 7811d4 Hao, Xudong
2010-03-24 15:17 ` Avi Kivity [this message]
2010-03-26 8:39 ` Hao, Xudong
2010-03-26 9:54 ` Avi Kivity
2010-03-28 9:03 ` Hao, Xudong
2010-03-28 9:09 ` 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=4BAA2D0E.1010606@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=xudong.hao@intel.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 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.