From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>,
m.hamayun@virtualopensystems.com
Cc: VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
qemu-devel@nongnu.org, kvmarm@lists.cs.columbia.edu
Subject: Re: [Qemu-devel] [PATCH 0/6][RFC] AArch64 support for Versatile Express using KVM
Date: Fri, 28 Jun 2013 15:04:46 +0200 [thread overview]
Message-ID: <51CD89EE.9080002@suse.de> (raw)
In-Reply-To: <CAFEAcA9NsMHvW5ixrKoiOnOxYDEz_qWR+UY78EPESD-bqcECnA@mail.gmail.com>
Am 28.06.2013 14:44, schrieb Peter Maydell:
> On 28 June 2013 13:20, Mian M. Hamayun <m.hamayun@virtualopensystems.com> wrote:
>> 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.
>
> This rather overlaps with a bunch of work John Rigby has already done
> (though not yet published to the mailing lists):
>
> https://git.linaro.org/gitweb?p=people/pmaydell/qemu-aarch64.git;a=shortlog;h=refs/heads/kvm-aarch64-wip
>
> so now we need to reconcile the two trees. If you'd let us know
> you were doing this a bit earlier we could probably have
> coordinated something...
I had been looking into that tree myself, and apart from John's
Linux'ish "ARM: " prefixes rather than our usual "target-arm: " (part of
which you forgot to fix before sending a PULL), I am really opposed to
copying A15MPCore_priv for A57. I plan to post a cleanup for the A9
version the weekend, now that we have a more elaborate hw/ directory
structure for headers.
Also I would really prefer to have the is_aarch64() helper operate on
ARMCPU rather than CPUARMState. QOM cast removal is underway to make
that more efficient.
Is there a 32-bit aarch64 register in ARMv8 to be accessed by TCG? If
not, the field should be in ARMCPU and a bool rather than uint32_t.
Regards,
Andreas
P.S. This cover letter got submitted separate from the actual patches so
that they are not marked RFC - please use --subject-prefix="RFC" or the
like and suggest to indicate there against which tree it is.
--
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-06-28 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 12:20 [Qemu-devel] [PATCH 0/6][RFC] AArch64 support for Versatile Express using KVM Mian M. Hamayun
2013-06-28 12:44 ` Peter Maydell
2013-06-28 13:04 ` Andreas Färber [this message]
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=51CD89EE.9080002@suse.de \
--to=afaerber@suse.de \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=m.hamayun@virtualopensystems.com \
--cc=peter.maydell@linaro.org \
--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).