All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -kernel-kqemu
Date: Thu, 09 Feb 2006 16:01:34 -0600	[thread overview]
Message-ID: <43EBBBBE.3070604@us.ibm.com> (raw)
In-Reply-To: <20060209180531.GA13429@jbrown.mylinuxbox.org>

Jim C. Brown wrote:
> -kernel-kqemu virtualizes ring 0 code.
>
> So it basically makes qemu do what VMware does.
>
> IIRC someone reported a 33% speedup with the new option.
>   
That was me.  That was a 33% speedup on win2k startup time.  kqemu (user 
only) has a negligible impact on win2k startup time which suggests this 
is mostly ring 0 code running which would make it a good benchmark for 
kernel-kqemu performance.

This was a terribly unscientific benchmarking so don't read too much 
into it.

Regards,

Anthony Liguori

  reply	other threads:[~2006-02-09 22:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 23:04 [Qemu-devel] -kernel-kqemu Jim C. Brown
2006-02-09  1:27 ` Jim C. Brown
2006-02-09  8:46   ` Hetz Ben Hamo
2006-02-09 18:05     ` Jim C. Brown
2006-02-09 22:01       ` Anthony Liguori [this message]
2006-02-09 23:32         ` Phil Krylov
2006-02-10 14:24           ` G Portokalidis
2006-04-19 17:31         ` Troy Benjegerdes
2006-04-21 21:09           ` Brad Campbell
2006-04-24  8:38             ` [Qemu-devel] -kernel-kqemu - bug with -m 256 Dan Sandberg
2006-04-24 13:28               ` [Qemu-devel] -kernel-kqemu - bug with -m 256 <-please disregard Dan Sandberg
2006-04-24 22:31             ` [Qemu-devel] -kernel-kqemu Fabrice Bellard
2006-02-09 18:35     ` Anthony Liguori
2006-02-09 22:01       ` Fabrice Bellard
2006-02-11  3:02         ` Kazu
2006-02-09 16:27 ` Brad Campbell
2006-02-10 13:29 ` Christian MICHON
2006-02-10 16:18   ` Jim C. Brown

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=43EBBBBE.3070604@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.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.