From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:36817) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QOAn7-0000YU-Ho for qemu-devel@nongnu.org; Sun, 22 May 2011 11:42:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QOAn6-0005Zr-Mv for qemu-devel@nongnu.org; Sun, 22 May 2011 11:42:05 -0400 Received: from mail-yi0-f45.google.com ([209.85.218.45]:37263) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QOAn6-0005Zn-JH for qemu-devel@nongnu.org; Sun, 22 May 2011 11:42:04 -0400 Received: by yib19 with SMTP id 19so2140375yib.4 for ; Sun, 22 May 2011 08:42:03 -0700 (PDT) Message-ID: <4DD92EC9.9060708@codemonkey.ws> Date: Sun, 22 May 2011 10:42:01 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <4DD3D236.90708@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> <4DD51FDA.3010107@codemonkey.ws> <4DD520ED.8010606@redhat.com> <4DD5260A.1080309@codemonkey.ws> <4DD5272F.5000003@siemens.com> <4DD52848.6030102@codemonkey.ws> <4DD52910.4080106@siemens.com> <4DD52B0E.2080604@codemonkey.ws> <4DD52BF2.2080506@redhat.com> <4DD54611.6090505@codemonkey.ws> <4DD62E01.5010600@redhat.com> <4DD689BA.8020106@codemonkey.ws> <4DD68FE5.1010506@siemens.com> <4DD8BD86.4010106@redhat.com> In-Reply-To: <4DD8BD86.4010106@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/22/2011 02:38 AM, Avi Kivity wrote: > On 05/20/2011 06:59 PM, Jan Kiszka wrote: >> > >> > Jan had mentioned previously about registering a new temporary window. >> > I assume the registration always gets highest_priority++, or do you >> have >> > to explicitly specify that PCI container gets priority=1? >> >> The latter. >> >> And I really prefer to have this explicit over deriving the priority >> from the registration order. That's way too fragile/unhandy. If you >> decide to replace a region of lower priority later on, you need to >> reregister everything at that level. > > Exactly. So priority is equivalent to registration order except it's explicit? So this is more palatable to me but I do prefer registration order since it promises less. But that said, this is a relatively minor feature IMHO given that I now understand the scope so I'm not going to object strongly. Regards, Anthony Liguori