From: Peter Maydell <peter.maydell@linaro.org>
To: "Chalamarla, Tirumalesh" <Tirumalesh.Chalamarla@caviumnetworks.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU on ARM64
Date: Sat, 1 Mar 2014 00:28:21 +0000 [thread overview]
Message-ID: <CAFEAcA-uHPicBbnJSyGG41nKn1_QrfocAa7-ap6AjO_RuR70ZQ@mail.gmail.com> (raw)
In-Reply-To: <90d26803e7524ec6b6508d00d7b4557d@BLUPR07MB195.namprd07.prod.outlook.com>
On 28 February 2014 07:08, Chalamarla, Tirumalesh
<Tirumalesh.Chalamarla@caviumnetworks.com> wrote:
> Is there any one, trying out cross compiling and running qemu
> on aarch64 host. if so is there a development branch where this wrok is
> progressing.
>
> Some one could please let me know the plan/time frame, for
> qemu on arm64 hosts running arm64 guests.
It's not entirely clear which of the various possible QEMU aarch64
setups you're interested in. Summary:
(1) using QEMU on aarch64 hosts to emulate other CPU architectures
(eg x86, MIPS): this went into QEMU about six months ago and was
in the last release of QEMU (1.7)
(2) using QEMU on aarch64 hosts as the userspace component
of a VM using KVM kernel support to run an aarch64 guest: this
should work with current QEMU, though some functionality (for
instance, migration) is not yet implemented
(3) using QEMU to emulate individual Linux AArch64 binaries, running
on any host (typically x86): this works in current upstream master, but
some instructions (parts of SIMD) are not yet implemented. I hope
we'll get the SIMD coverage completed within the next few weeks,
in time to put it into QEMU 2.0.
(4) using QEMU to emulate an entire AArch64 system that can
boot a guest kernel, typically running on an x86 host: we're
working on this right now; we have work-in-progress code which
will boot a kernel and are working on cleaning it up to upstream
quality. I expect we'll have this done within a month or two, but
it won't make it into the QEMU 2.0 release (slightly too late).
I'm guessing you're interested in (2) or maybe (1). For (2),
kvmarm@lists.cs.columbia.edu is a good list to follow to
monitor what's currently going on.
thanks
-- PMM
next prev parent reply other threads:[~2014-03-01 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 7:08 [Qemu-devel] QEMU on ARM64 Chalamarla, Tirumalesh
2014-03-01 0:28 ` Peter Maydell [this message]
2014-03-01 0:41 ` Xuebing wang
2014-03-01 0:45 ` Peter Maydell
2014-03-01 4:36 ` Chalamarla, Tirumalesh
2014-03-01 10:42 ` Peter Maydell
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=CAFEAcA-uHPicBbnJSyGG41nKn1_QrfocAa7-ap6AjO_RuR70ZQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=Tirumalesh.Chalamarla@caviumnetworks.com \
--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).