From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38907) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ya0Xw-0000Uo-9U for qemu-devel@nongnu.org; Mon, 23 Mar 2015 07:29:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ya0Xt-0005cV-67 for qemu-devel@nongnu.org; Mon, 23 Mar 2015 07:29:28 -0400 Received: from mail.tu-berlin.de ([130.149.7.33]:65390) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ya0Xs-0005cJ-Vw for qemu-devel@nongnu.org; Mon, 23 Mar 2015 07:29:25 -0400 Message-ID: <550FF910.1070008@mailbox.tu-berlin.de> Date: Mon, 23 Mar 2015 12:29:20 +0100 From: Merten Sach MIME-Version: 1.0 References: <550C581D.5070609@mailbox.tu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] GSoC Proposal: ARM Virtualization Extensions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: "Edgar E. Iglesias" , QEMU Developers On 20/03/15 18:44, Peter Maydell wrote: > * having a project plan that divides the work up into small > but coherent chunks that can be landed upstream incrementally > (to avoid the failure mode of "work all summer but don't > get it finished, and so don't have anything concrete > to show for it at the end") Hi, what is the policy for incomplete specification implementations? For example, I could imagine implementing mode switches and exception routing without nested paging (though Sergey already implemented it). This would not be sufficient to run KVM. However one could test it. Best regards, Merten