From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55245) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UtkC6-0006He-Cz for qemu-devel@nongnu.org; Mon, 01 Jul 2013 15:55:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UtkC0-0002jL-5w for qemu-devel@nongnu.org; Mon, 01 Jul 2013 15:55:26 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:33922) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UtjsZ-00005n-0F for qemu-devel@nongnu.org; Mon, 01 Jul 2013 15:35:15 -0400 Received: by mail-wi0-f176.google.com with SMTP id ey16so3441453wid.9 for ; Mon, 01 Jul 2013 12:35:13 -0700 (PDT) Message-ID: <51D1D9F0.9060109@virtualopensystems.com> Date: Mon, 01 Jul 2013 21:35:12 +0200 From: "Mian M. Hamayun" MIME-Version: 1.0 References: <51CD7F88.2060704@virtualopensystems.com> <51CD89EE.9080002@suse.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH 0/6][RFC] AArch64 support for Versatile Express using KVM Reply-To: m.hamayun@virtualopensystems.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: VirtualOpenSystems Technical Team , kvmarm@lists.cs.columbia.edu, =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , qemu-devel@nongnu.org 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 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