From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -kernel-kqemu
Date: Thu, 09 Feb 2006 12:35:41 -0600 [thread overview]
Message-ID: <43EB8B7D.5020901@us.ibm.com> (raw)
In-Reply-To: <41e41e7a0602090046p18e89050m79c914f5293b2ade@mail.gmail.com>
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?
>
I can take a stab although hopefully Fabrice will post something in the
near future..
kqemu and qvm86 allow ring 3 code to run on bare metal. For ring 0
code, both defer to qemu which does binary translation.
-kernel-kqemu allows portions of ring 0 code to run on bare metal.
Presumably, this means kqemu now has a block scanner and can determine
whether or not a block contains sensitive instructions. It could be
interpreting those blocks or it may just always return to qemu--it's
unclear since kqemu is not open source.
The changes in qemu just allow for kqemu to try and execute ring 0 code
it seems. All the interesting changes are probably in kqemu itself...
Regards,
Anthony Liguori
> Thanks,
> Hetz
>
> On 2/9/06, Jim C. Brown <jma5@umd.edu> wrote:
>
>> On Wed, Feb 08, 2006 at 06:04:35PM -0500, Jim C. Brown wrote:
>>
>>> This sounds like an interesting option. Qemu has moved one step closer to
>>> VMware...
>>>
>>>
>> I should probably add, that this new option (-kernel-kqemu) allows for speeds
>> very close to VMware because it allows kqemu to virtualize most ring 0 code
>> (in addition to ring 3 code).
>>
>> Can't wait to see qvm86 make use of the new API.
>>
>>
>>> --
>>> Infinite complexity begets infinite beauty.
>>> Infinite precision begets infinite perfection.
>>>
>>>
>>> _______________________________________________
>>> Qemu-devel mailing list
>>> Qemu-devel@nongnu.org
>>> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>>>
>>>
>> --
>> Infinite complexity begets infinite beauty.
>> Infinite precision begets infinite perfection.
>>
>>
>> _______________________________________________
>> Qemu-devel mailing list
>> Qemu-devel@nongnu.org
>> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>>
>>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
next prev parent reply other threads:[~2006-02-09 18:36 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
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 [this message]
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=43EB8B7D.5020901@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 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).