From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:37023) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN3bK-00038o-Ry for qemu-devel@nongnu.org; Thu, 19 May 2011 09:49:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QN3bJ-0001Fm-TF for qemu-devel@nongnu.org; Thu, 19 May 2011 09:49:18 -0400 Received: from mail-yx0-f173.google.com ([209.85.213.173]:61097) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QN3bJ-0001Fi-PQ for qemu-devel@nongnu.org; Thu, 19 May 2011 09:49:17 -0400 Received: by yxk8 with SMTP id 8so1056016yxk.4 for ; Thu, 19 May 2011 06:49:17 -0700 (PDT) Message-ID: <4DD51FDA.3010107@codemonkey.ws> Date: Thu, 19 May 2011 08:49:14 -0500 From: Anthony Liguori 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> In-Reply-To: <4DD51B64.8000306@redhat.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: Avi Kivity Cc: Jan Kiszka , qemu-devel , Gleb Natapov On 05/19/2011 08:30 AM, Avi Kivity wrote: > On 05/19/2011 04:26 PM, Jan Kiszka wrote: >> On 2011-05-19 15:07, Avi Kivity wrote: >> And when introducing hierarchical registration, we will have to go >> through all of this once again. Plus the API may have to be changed >> again if it does not fulfill all requirements of the hierarchical region >> management. And we have no proof that it allows an efficient core >> implementation. > > This API *is* hierarchical registration. v2 will (hopefully) prove that > it can be done efficiently. We also need hierarchical dispatch. Priorities are just a weak attempt to emulate hierarchical dispatch but I don't think there's an improvement over a single dispatch table. Hierarchical dispatch is simpler. You just need a simple list at each bus. I don't see a strong need to tie anything to qdev here FWIW. Regards, Anthony Liguori