From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [announce] [patch] KVM paravirtualization for Linux
Date: Sat, 6 Jan 2007 13:08:18 +0000 [thread overview]
Message-ID: <20070106130817.GB5660@ucw.cz> (raw)
In-Reply-To: <20070105215223.GA5361-X9Un+BFzKDI@public.gmane.org>
Hi!
> i'm pleased to announce the first release of paravirtualized KVM (Linux
> under Linux), which includes support for the hardware cr3-cache feature
> of Intel-VMX CPUs. (which speeds up context switches and TLB flushes)
>
> the patch is against 2.6.20-rc3 + KVM trunk and can be found at:
>
> http://redhat.com/~mingo/kvm-paravirt-patches/
>
> Some aspects of the code are still a bit ad-hoc and incomplete, but the
> code is stable enough in my testing and i'd like to have some feedback.
>
> Firstly, here are some numbers:
>
> 2-task context-switch performance (in microseconds, lower is better):
>
> native: 1.11
> ----------------------------------
> Qemu: 61.18
> KVM upstream: 53.01
> KVM trunk: 6.36
> KVM trunk+paravirt/cr3: 1.60
Does this make Xen obsolete? I mean... we have xen patches in suse
kernels, should we keep updating them, or just drop them in favour of
KVM?
Pavel
--
Thanks for all the (sleeping) penguins.
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-01-06 13:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 21:52 [announce] [patch] KVM paravirtualization for Linux Ingo Molnar
2007-01-05 23:02 ` [kvm-devel] " Anthony Liguori
[not found] ` <20070105215223.GA5361-X9Un+BFzKDI@public.gmane.org>
2007-01-05 22:15 ` Zachary Amsden
[not found] ` <459ECDF7.9040309-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2007-01-05 22:30 ` Ingo Molnar
[not found] ` <20070105223009.GA15369-X9Un+BFzKDI@public.gmane.org>
2007-01-05 22:50 ` Zachary Amsden
2007-01-05 23:28 ` Ingo Molnar
2007-01-06 13:08 ` Pavel Machek [this message]
[not found] ` <20070106130817.GB5660-+ZI9xUNit7I@public.gmane.org>
2007-01-07 18:29 ` Christoph Hellwig
2007-01-08 18:18 ` Christoph Lameter
2007-01-07 12:20 ` Avi Kivity
[not found] ` <45A0E586.50806-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-07 17:42 ` Hollis Blanchard
2007-01-07 17:44 ` Ingo Molnar
[not found] ` <20070107174416.GA14607-X9Un+BFzKDI@public.gmane.org>
2007-01-08 8:22 ` Avi Kivity
[not found] ` <45A1FF4E.1020106-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-08 8:39 ` Ingo Molnar
[not found] ` <20070108083935.GB18259-X9Un+BFzKDI@public.gmane.org>
2007-01-08 9:08 ` Avi Kivity
[not found] ` <45A20A0A.70403-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-08 9:18 ` Ingo Molnar
[not found] ` <20070108091819.GB26587-X9Un+BFzKDI@public.gmane.org>
2007-01-08 9:31 ` Avi Kivity
[not found] ` <45A20F60.20207-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-08 9:43 ` Ingo Molnar
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=20070106130817.GB5660@ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-X9Un+BFzKDI@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