From: "Jim C. Brown" <jma5@umd.edu>
To: Hetz Ben Hamo <hetzbh@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -kernel-kqemu
Date: Thu, 9 Feb 2006 13:05:31 -0500 [thread overview]
Message-ID: <20060209180531.GA13429@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <41e41e7a0602090046p18e89050m79c914f5293b2ade@mail.gmail.com>
On Thu, Feb 09, 2006 at 10:46:07AM +0200, Hetz Ben Hamo wrote:
> Hi,
>
> I?m sorry, but I?ve been following the CVS commits and I haven?t
> understood this new option (fabrice has not written anything to this
> list about it and what it does for the end user).
>
> Could someone please shed some light for me and others who didn?t
> understand whats going on please?
>
> Thanks,
> Hetz
>
-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.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2006-02-09 18:05 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 [this message]
2006-02-09 22:01 ` Anthony Liguori
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=20060209180531.GA13429@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=hetzbh@gmail.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 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).