From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:41678) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QrAOA-0002A4-VJ for qemu-devel@nongnu.org; Wed, 10 Aug 2011 11:08:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QrAO8-0004gh-Qa for qemu-devel@nongnu.org; Wed, 10 Aug 2011 11:08:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56612) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QrAO8-0004gU-Id for qemu-devel@nongnu.org; Wed, 10 Aug 2011 11:08:08 -0400 Message-ID: <4E429ED4.4040707@redhat.com> Date: Wed, 10 Aug 2011 18:08:04 +0300 From: Avi Kivity MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Memory API feature page List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel , KVM list While the memory API is not a feature, it deserves a feature page, so I can put the TODO list there: http://wiki.qemu.org/Features/Memory_API Please consider helping out. Device conversions are easy, if boring, and there's no end to them. There is a lot of more interesting work on the core itself, but I'd like to defer it until conversion is complete. -- error compiling committee.c: too many arguments to function