From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Zhao, Yunfeng" <yunfeng.zhao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Test result for KVM60RC1
Date: Wed, 23 Jan 2008 14:37:18 +0200 [thread overview]
Message-ID: <479734FE.3070405@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A02AF16E8-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Zhao, Yunfeng wrote:
>>
>> And it's now fixed, kvm-userspace 76640d2815c628f23351e2c96c48c9e505e2d83e.
>>
> Quick fix again.:) We will retest it in next testing.
> Will this fix affect performance of the guest?
>
>
Hopefully not. Windows smp boots quickly, and I also ran a uniprocessor
I/O benchmark on Linux (fio).
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-01-23 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 5:42 Test result for KVM60RC1 Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02AF14F3-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-23 8:50 ` Avi Kivity
[not found] ` <4796FFEB.6010402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-23 9:00 ` Zhao, Yunfeng
2008-01-23 9:03 ` Avi Kivity
[not found] ` <479702D7.5080503-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-23 11:40 ` Avi Kivity
[not found] ` <479727A9.70800-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-23 12:04 ` Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02AF16E8-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-23 12:37 ` Avi Kivity [this message]
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=479734FE.3070405@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=yunfeng.zhao-ral2JQCrhuEAvxtiuMwx3w@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 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.