qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Mian M. Hamayun" <m.hamayun@virtualopensystems.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "VirtualOpenSystems Technical Team" <tech@virtualopensystems.com>,
	kvmarm@lists.cs.columbia.edu, "Andreas Färber" <afaerber@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6][RFC] AArch64 support for Versatile Express using KVM
Date: Mon, 01 Jul 2013 21:35:12 +0200	[thread overview]
Message-ID: <51D1D9F0.9060109@virtualopensystems.com> (raw)
In-Reply-To: <CAFEAcA-4VXkQ93o7Nihwa4-Kkz-zjyOkEWcrMc7M_VrfTpB1Tw@mail.gmail.com>

At the time we started working on AArch64, we were not certain that our 
implementation would be published in near future. Now that this is 
cleared up we are more than happy to coordinate together.
> On 28 June 2013 14:04, Andreas Färber <afaerber@suse.de> wrote:
>> 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 agree that just copying A15 is wrong (among other things, we
> should be modelling the hardware, not just "this seems to make
> KVM not barf"). That's one of the reasons I hadn't sent the patch
> set out yet.
>
Initially we thought about this aspect too, but in order to get started, 
we made the choice to continue using the already available A15 part as 
is. Obviously this is an RFC patch series and we would like to have your 
opinion on how we can proceed from here, based on the working solution 
that we have now, although we may have some differences from the real 
hardware.
>> 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.
> This also needs looking at, yes.
>
> -- PMM
--
Hamayun

  reply	other threads:[~2013-07-01 19:55 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
2013-06-28 13:07     ` Peter Maydell
2013-07-01 19:35       ` Mian M. Hamayun [this message]
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=51D1D9F0.9060109@virtualopensystems.com \
    --to=m.hamayun@virtualopensystems.com \
    --cc=afaerber@suse.de \
    --cc=kvmarm@lists.cs.columbia.edu \
    --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).