From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38857) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNLch-0006GZ-G6 for qemu-devel@nongnu.org; Fri, 20 May 2011 05:03:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QNLcg-0006Yw-KB for qemu-devel@nongnu.org; Fri, 20 May 2011 05:03:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:10495) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QNLcg-0006Ys-9N for qemu-devel@nongnu.org; Fri, 20 May 2011 05:03:54 -0400 Message-ID: <4DD62E74.9020804@redhat.com> Date: Fri, 20 May 2011 12:03:48 +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> <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> <4DD546DC.1000703@siemens.com> <4DD5477D.7090706@codemonkey.ws> In-Reply-To: <4DD5477D.7090706@codemonkey.ws> 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: Anthony Liguori Cc: Jan Kiszka , qemu-devel , Gleb Natapov On 05/19/2011 07:38 PM, Anthony Liguori wrote: >> You can always create a new memory region with higher priority, pointing >> to the RAM window you want to have above VGA. That's what we do today as >> well, just with different effects on the internal representation. > > > But then we're no better than we are today. I thought the whole point > of this thread of discussion was to allow overlapping I/O regions to > be handled in a better way than we do today? It is, and the goal is achieved. Right now the code saves the old contents in isa_page_descs. With the new approach it calls memory_region_del_subregion() and the previous contents magically appear (or new contents if they changed in the meanwhile). -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.