From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH 4/10] Trivial: Make decode_register() static
Date: Tue, 17 Jul 2007 16:43:54 +0300 [thread overview]
Message-ID: <469CC79A.8000503@qumranet.com> (raw)
In-Reply-To: <469C8B870200005A00027AE6-Igcdv/6uVdMHoYOw/+koYqIwWpluYiW7@public.gmane.org>
Gregory Haskins wrote:
> On Tue, 2007-07-17 at 23:16 +1000, Rusty Russell wrote:
>
>> I have shied away from touching x86_emulate.c (it could definitely use
>> some love, but it is forked from the Xen code, and it would be more
>> productive to cross-merge fixes).
>>
>
> On this topic, here's an idea I have been kicking around for a while:
>
> If the x86_emulate code is so buggy/incomplete, and the QEMU one seems
> to be able to generally handle most situations...could we simply exit to
> userspace and use the qemu emulator somehow? I realize the overhead is
> greater, but slow+working is > fast+broken in my book ;)
>
> Perhaps a hybrid solution would work? E.g. exit to qemu emulator when
> the in-kernel stuff hits a mis-emulation point (do we realize this
> consciously in the code, or only after the guest crashes?)
>
> I'm not really sure if this is plausible. Its just something I was
> thinking about.
>
>
It was once done that way (we started by having qemu emulate 32- and 16-
bit code, then just 16-, then nothing). However, I'd like kvm to be
independent of an external emulator, so that all cpu emulation is done
in kernel.
Of course we have to have an in-kernel emulator, for page tables and for
in-kernel mmio, so having a partial emulator in kernel and a full
emulator in userspace seems messy.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-07-17 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 13:27 [PATCH 4/10] Trivial: Make decode_register() static Gregory Haskins
[not found] ` <469C8B870200005A00027AE6-Igcdv/6uVdMHoYOw/+koYqIwWpluYiW7@public.gmane.org>
2007-07-17 13:38 ` Dor Laor
2007-07-17 13:41 ` Anthony Liguori
[not found] ` <469CC6FB.9050308-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-07-17 13:53 ` Mike Day
2007-07-17 13:43 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-17 13:12 [PATCH 1/10] Trivial: /dev/kvm interface is no longer experimental Rusty Russell
2007-07-17 13:14 ` [PATCH 2/10] Trivial: Remove KVM_IRQ_BITMAP macro Rusty Russell
2007-07-17 13:15 ` [PATCH 3/10] Trivial: Remove unused struct cpu_user_regs declaration Rusty Russell
[not found] ` <1184678129.10380.10.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-07-17 13:16 ` [PATCH 4/10] Trivial: Make decode_register() static Rusty Russell
[not found] ` <1184678171.10380.12.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-07-17 13:29 ` Avi Kivity
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=469CC79A.8000503@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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