qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Hollis Blanchard" <hollis@alumni.cmu.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Status on ARM host cpu
Date: Mon, 17 Nov 2008 10:32:41 -0600	[thread overview]
Message-ID: <fb412d760811170832g7f9e4ccbvd128f7b66e445139@mail.gmail.com> (raw)
In-Reply-To: <gfmotq$smi$1@ger.gmane.org>

On Sat, Nov 15, 2008 at 9:12 AM, Steffen Liebergeld <usenet@gmx.eu> wrote:
> Hi Paul,
>
> Paul Brook <paul@codesourcery.com> schrieb:
>> On Friday 14 November 2008, Steffen Liebergeld wrote:
>>> Hi,
>>>
>>> I am currently researching of whether or not it is feasible to port kqemu
>>> to the ARM platform. The website says qemu on ARM hosts is in
>>> "testing"-state. Does that still apply to the latest svn-Version?
>>
>> Should just about work, though you should expect bugs.
>
>> However I advise using KVM and not kqemu. KVM has already been merged to
>> upstream kernels, and the chances of getting another hypervisor interface
>> merged are approximately zero.
>
> KVM is not an option for me (and is not available for the ARM-platform).
>
> I plan to port kqemu for the ARM-platform. Do have any estimates, for how much
> work would be needed to adopt the kqemu-Interface of qemu (which is
> x86-centric) to ARM (ignoring the effort needed to port the
> kqemu-kernel-module)?

To expand on what Jan said, I've implemented KVM on PowerPC 440 core,
which has no hardware virtualization support. I expect you're in the
same situation on ARM.

Basically you execute most guest instructions natively in hardware,
running in user mode. When the guest kernel attempts to perform a
privileged operation, you trap to supervisor mode and emulate it.
(Optionally, you can also patch the guest to prevent it from
attempting that operation in the first place.)

This is very feasible given the KVM interface -- the 440 support is
already working and merged upstream. I would strongly recommend
working with KVM instead of kqemu, if for no other reason than KVM has
a development community which can help you, and kqemu doesn't.

-Hollis

      parent reply	other threads:[~2008-11-17 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14  8:32 [Qemu-devel] Status on ARM host cpu Steffen Liebergeld
2008-11-14 14:15 ` Paul Brook
2008-11-15 15:12   ` [Qemu-devel] " Steffen Liebergeld
2008-11-15 22:21     ` Jan Kiszka
2008-11-17 16:32     ` Hollis Blanchard [this message]

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=fb412d760811170832g7f9e4ccbvd128f7b66e445139@mail.gmail.com \
    --to=hollis@alumni.cmu.edu \
    --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).