From: Christoffer Dall <christoffer.dall@linaro.org>
To: Greg Bellows <greg.bellows@linaro.org>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/4] target-arm: ARM64: Adding EL1 AARCH32 guest support
Date: Mon, 26 Jan 2015 12:03:59 +0100 [thread overview]
Message-ID: <20150126110359.GN15076@cbox> (raw)
In-Reply-To: <1421866193-24941-1-git-send-email-greg.bellows@linaro.org>
On Wed, Jan 21, 2015 at 12:49:49PM -0600, Greg Bellows wrote:
> Added support for running an AArch32 guest on a AArch64 KVM host. Support has
> only been added to the QEMU machvirt machine. The addition of CPU properties
> specifiable from the command line were added to allow disablement of AArch64
> execution state hereby forcing EL1 to be AArch32. The new CPU command line
> property is "aarch64=on/off" that is specified as follows:
>
> aarch64-softmmu/qemu-system-aarch64 -M virt -cpu cortex-a57,aarch64=off ...
>
This patch set seems to break standard aarch64 KVM guest functionality,
I never see my guest progressing....
-Christoffer
next prev parent reply other threads:[~2015-01-26 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 18:49 [Qemu-devel] [PATCH v2 0/4] target-arm: ARM64: Adding EL1 AARCH32 guest support Greg Bellows
2015-01-21 18:49 ` [Qemu-devel] [PATCH v2 1/4] target-arm: Add CPU property to disable AArch64 Greg Bellows
2015-01-21 18:49 ` [Qemu-devel] [PATCH v2 2/4] target-arm: Add feature parsing to virt Greg Bellows
2015-01-21 18:49 ` [Qemu-devel] [PATCH v2 3/4] target-arm: Add 32/64-bit register sync Greg Bellows
2015-01-27 21:20 ` Christoffer Dall
2015-01-27 21:40 ` Greg Bellows
2015-01-21 18:49 ` [Qemu-devel] [PATCH v2 4/4] target-arm: Add AArch32 guest support to KVM64 Greg Bellows
2015-01-27 21:21 ` Christoffer Dall
2015-01-27 22:23 ` Greg Bellows
2015-01-26 11:03 ` Christoffer Dall [this message]
2015-01-26 15:44 ` [Qemu-devel] [PATCH v2 0/4] target-arm: ARM64: Adding EL1 AARCH32 guest support Greg Bellows
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=20150126110359.GN15076@cbox \
--to=christoffer.dall@linaro.org \
--cc=greg.bellows@linaro.org \
--cc=peter.maydell@linaro.org \
--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).