From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33296) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN3ZK-0001ft-MZ for qemu-devel@nongnu.org; Thu, 19 May 2011 09:47:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QN3ZG-00012m-6H for qemu-devel@nongnu.org; Thu, 19 May 2011 09:47:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4491) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN3ZF-00012h-SK for qemu-devel@nongnu.org; Thu, 19 May 2011 09:47:10 -0400 Message-ID: <4DD51F58.2020807@redhat.com> Date: Thu, 19 May 2011 16:47:04 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4DD3D236.90708@siemens.com> <4DD3D95E.2060105@redhat.com> <4DD3E1B3.3020405@siemens.com> <4DD3E47F.9060104@redhat.com> <4DD3E782.8090208@siemens.com> <4DD3E8D6.6090807@redhat.com> <20110519090851.GD28399@redhat.com> <4DD4DE8E.8030402@redhat.com> <20110519091404.GE28399@redhat.com> <4DD5029D.6000700@redhat.com> <20110519115405.GG28399@redhat.com> <4DD505C4.6010604@redhat.com> <4DD50B17.7000205@siemens.com> <4DD511FB.3080901@redhat.com> <4DD51413.1050202@siemens.com> <4DD51468.7050509@redhat.com> <4DD51531.7000701@siemens.com> <4DD515F9.1020902@redhat.com> <4DD51A82.7060205@siemens.com> <4DD51B64.8000306@redhat.com> <4DD51E9A.9020604@siemens.com> In-Reply-To: <4DD51E9A.9020604@siemens.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] Memory API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: qemu-devel , Gleb Natapov On 05/19/2011 04:43 PM, Jan Kiszka wrote: > > > > I feel a lot less comfortable about it since it introduces more > > variables. It also means a full conversion is impossible. > > > > While doing it in one pass reduces the total effort, it increases the > > risk IMO. > > If we are sure we can reasonably evolve from this conversion level and > it will still fit the final model, then we may take that route. If you > want to go that way, OK, let's see what v2 will bring. We should use the > meantime and try to further develop the long-term APIs. > Yes. This way people who are familiar with qdev and non-x86 can look at the API and the partial conversion and see if something is missing. -- error compiling committee.c: too many arguments to function