From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:48333) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T4b2s-0004p3-AO for qemu-devel@nongnu.org; Thu, 23 Aug 2012 13:18:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T4b2r-0004O4-22 for qemu-devel@nongnu.org; Thu, 23 Aug 2012 13:18:14 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:19030) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T4b2q-0004Ny-Tq for qemu-devel@nongnu.org; Thu, 23 Aug 2012 13:18:12 -0400 Message-ID: <50366602.4030106@citrix.com> Date: Thu, 23 Aug 2012 18:18:58 +0100 From: Julien Grall MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [QEMU][RFC V2 05/10] xen-memory: register memory/IO range in Xen List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefano Stabellini Cc: "christian.limpach@gmail.com" , "qemu-devel@nongnu.org" , "xen-devel@lists.xen.org" On 08/23/2012 03:41 PM, Stefano Stabellini wrote: > On Wed, 22 Aug 2012, Julien Grall wrote: > >> Add Memory listener on IO and modify the one on memory. >> Becareful, the first listener is not called is the range is still register with >> register_ioport*. So Xen will never know that this QEMU is handle the range. >> > I don't understand what you mean here. Could you please elaborate? > I made a patch series to remove all ioport_register_* function in differents devices (dma, cirrus, ...): https://lists.gnu.org/archive/html/qemu-devel/2012-08/msg04007.html ioport_register_* don' t use the new memory API, so listener is not called when a new range is registered. I will rework the commit message and send it back. -- Julien