From: "Andreas Färber" <afaerber@suse.de>
To: Lior Vernia <liorvern@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Potential to accelerate QEMU for specific architectures
Date: Sun, 26 May 2013 11:00:54 +0200 [thread overview]
Message-ID: <51A1CF46.5050906@suse.de> (raw)
In-Reply-To: <CALBwSP39qnyENkvj4PtySHYnfVc7tkc6wM0nAxDsw5AtiEG=FA@mail.gmail.com>
Am 26.05.2013 07:40, schrieb Lior Vernia:
> On Sat, May 25, 2013 at 10:06 PM, Andreas Färber <afaerber@suse.de> wrote:
>> Am 24.05.2013 21:24, schrieb Lior Vernia:
>>> I am running x86 applications on an ARM device using QEMU, and found
>>> it too slow for my needs.
>>
>> Before we start going into technical details, what are you trying to
>> achieve on a high level and how did you try to do it?
>>
>> Are you using qemu-system-x86_64 or qemu-x86_64? The latest v1.5.0?
>
> Sorry, right after I wrote the message it occured to me I should have
> mentioned that I was talking about qemu-system, either x86 or i386. At
> the moment I just ran the limbo app on a Galaxy SIII with various
> images, just to see the capabilities, and was disappointed. Limbo
> seems to run v1.1.0.
First time I hear of that app... v1.1.0 is a year old, many TCG
improvements have happened since. Suggest you contact the app's author
to get that updated to v1.5.0.
http://git.qemu.org/?p=qemu.git;a=history;f=tcg/arm;hb=HEAD
> If you suspect that it's the JNI wrapping that's causing a lot of the
> damage,
The UI (drawing) code could also be a potential bottleneck - but judging
from the files it looks as if the UI were just a Java VNC client, which
probably accesses a JNI-unaffected QEMU process?
http://code.google.com/p/limbo-android/source/browse/#git%2Fsrc
> then we can talk about compiling QEMU for ARM and running it
> natively, I just haven't been able to get that to work.
That would take some of the uncertainties out of the equation, yes.
You still haven't said what it is that you would like to do with system
emulation on your ARM device: Does it need to be x86? If you just want
access to a full Linux system from Android, you might be more interested
in investigating qemu-system-arm with KVM acceleration (requires
Cortex-A15 and 3.9+ kernel) - in practice virtualization will be faster
than anything binary translation can offer.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-05-26 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 19:24 [Qemu-devel] Potential to accelerate QEMU for specific architectures Lior Vernia
2013-05-25 17:48 ` Blue Swirl
2013-05-25 19:06 ` Andreas Färber
2013-05-25 21:16 ` Paolo Bonzini
2013-05-26 5:40 ` Lior Vernia
2013-05-26 9:00 ` Andreas Färber [this message]
2013-05-26 16:03 ` Lior Vernia
2013-05-26 9:26 ` Peter Maydell
2013-05-26 9:58 ` Gleb Natapov
2013-05-26 10:11 ` Peter Maydell
2013-05-26 16:35 ` Lior Vernia
2013-05-27 6:59 ` Paolo Bonzini
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=51A1CF46.5050906@suse.de \
--to=afaerber@suse.de \
--cc=liorvern@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).