From: Gleb Natapov <gleb@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Lior Vernia" <liorvern@gmail.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>,
陳韋任 <chenwj@iis.sinica.edu.tw>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] Potential to accelerate QEMU for specific architectures
Date: Sun, 26 May 2013 12:58:25 +0300 [thread overview]
Message-ID: <20130526095825.GR4725@redhat.com> (raw)
In-Reply-To: <CAFEAcA9Ce0XrEJb+CTSDCaU=1C2JmcHz4ZMt+aY-nr-mR3X4rg@mail.gmail.com>
On Sun, May 26, 2013 at 10:26:04AM +0100, Peter Maydell wrote:
> On 26 May 2013 06:40, Lior Vernia <liorvern@gmail.com> wrote:
> > 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.
>
> > I wanted to add that I've been reading about this Russian startup
> > that's looking to emulate x86 on ARM at 40% of native speed using
> > dynamic binary translation (as far as I gather):
> > http://www.bit-tech.net/news/hardware/2012/10/04/x86-on-arm/1
> > So this should be possible. And it can't be very much unlike QEMU, can it?
>
> That article suggests they're doing application-level translation,
> not system-level emulation. If you:
> * design your emulation from scratch with that use case in mind
> (qemu is system emulation first with app-level as a secondary case)
> * are happy to have just one guest and one target architecture
> (this is actually mostly useful in that it reduces the set of things
> you have to test; it also lets you take shortcuts in corner cases
> for your initial implementation)
> * put more concentrated effort into emulation performance than QEMU
>
> then you should be able to do better than qemu does currently.
> You'd probably end up with something like Transitive's QuickTransit/
> Rosetta.
>
Actually here is an example of Starcraft running in android on ARM in
full speed: http://forum.xda-developers.com/showthread.php?p=39009939
Search more about winulator.
--
Gleb.
next prev parent reply other threads:[~2013-05-26 9:58 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
2013-05-26 16:03 ` Lior Vernia
2013-05-26 9:26 ` Peter Maydell
2013-05-26 9:58 ` Gleb Natapov [this message]
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=20130526095825.GR4725@redhat.com \
--to=gleb@redhat.com \
--cc=afaerber@suse.de \
--cc=chenwj@iis.sinica.edu.tw \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.