From: "Mian M. Hamayun" <m.hamayun@virtualopensystems.com>
To: qemu-devel@nongnu.org
Cc: VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
kvmarm@lists.cs.columbia.edu
Subject: [Qemu-devel] [PATCH 0/6][RFC] AArch64 support for Versatile Express using KVM
Date: Fri, 28 Jun 2013 14:20:24 +0200 [thread overview]
Message-ID: <51CD7F88.2060704@virtualopensystems.com> (raw)
This patch series implements KVM support in QEMU for the ARMv8 Cortex
A57 CPU.
It depends on the previously submitted AArch64 Preparation Patchset V4,
and uses
as a base, the existing Versatile Express machine model and the already
available KVM in-kernel GIC support.
As a reference, KVM Tool and the AArch64 bootwrapper were used, as well as
public documentation from ARM. The following work has been tested with SMP
capabilities, under ARMv8 Fast Models and the Foundation model (Open
Embedded
userspace with an emulated MMC).
The work has been sponsored by Huawei, and developed in collaboration with
Huawei Technologies Duesseldorf GmbH, European Research Center Munich (ERC).
A working tree of this implementation is available on the "kvm-aarch64"
branch
of the following github repository.
https://github.com/virtualopensystems/qemu.git
Summary of Patches:
[PATCH 1/6] Added aarch64 configure support and default
[PATCH 2/6] Added KVM Headers from KVM Tool
[PATCH 3/6] Added Aarch64 CPU Initialization, Get and Put Registers
[PATCH 4/6] Added the Versatile Express Machine Model for A57
[PATCH 5/6] Added Boot Support for Aarch64 Processor.
[PATCH 6/6] Added SMP for Aarch64 Processors.
next reply other threads:[~2013-06-28 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 12:20 Mian M. Hamayun [this message]
2013-06-28 12:44 ` [Qemu-devel] [PATCH 0/6][RFC] AArch64 support for Versatile Express using KVM Peter Maydell
2013-06-28 13:04 ` Andreas Färber
2013-06-28 13:07 ` Peter Maydell
2013-07-01 19:35 ` Mian M. Hamayun
2013-09-02 9:46 ` Andreas Färber
2013-09-02 10:00 ` 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=51CD7F88.2060704@virtualopensystems.com \
--to=m.hamayun@virtualopensystems.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.com \
/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).