qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Status on ARM host cpu
Date: Sat, 15 Nov 2008 23:21:27 +0100	[thread overview]
Message-ID: <491F4B67.3000106@web.de> (raw)
In-Reply-To: <gfmotq$smi$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]

Steffen Liebergeld 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).

(...so is KQEMU)

> 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)?

You should start with studying both KVM and KQEMU in more details.
Before thinking about which interface to implement, first clarify what
approach you actually need for ARM. I don't think that arch is as weird
as x86. Virtualization-wise it will rather be close to PowerPC e.g. And
for PowerPC (440) there is already kvm support...

But even if you had to implement a KQEMU-comparable VMM for ARM, you
should definitely use KVM's interface and infrastructure (which goes
beyond KQEMU). Rather extend it if that's required. Only that way your
work would have a chance to become mainline and benefit from the ongoing
development in KVM and QEMU. Believe us. :)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2008-11-15 22:22 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 [this message]
2008-11-17 16:32     ` Hollis Blanchard

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=491F4B67.3000106@web.de \
    --to=jan.kiszka@web.de \
    --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).