From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [RFC v4 00/58] Memory API Date: Tue, 19 Jul 2011 19:01:16 +0200 Message-ID: <4E25B85C.1030809@siemens.com> References: <1310901265-32051-1-git-send-email-avi@redhat.com> <20110719135601.GA7194@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , qemu-devel@nongnu.org, kvm@vger.kernel.org To: "Michael S. Tsirkin" Return-path: Received: from thoth.sbs.de ([192.35.17.2]:21053 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751001Ab1GSRB2 (ORCPT ); Tue, 19 Jul 2011 13:01:28 -0400 In-Reply-To: <20110719135601.GA7194@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2011-07-19 15:56, Michael S. Tsirkin wrote: > On Sun, Jul 17, 2011 at 02:13:27PM +0300, Avi Kivity wrote: >> New in this version: >> MemoryRegionOps gained .old_mmio and .old_portio members, which allow >> reusing old-style callbacks with the new API. All uses were converted, >> except for eepro100.c, which uses the same MemoryRegionOps for both >> portio and mmio. Some intermediate patches do introduce dispatching >> callbacks, but they are removed later. >> >> Caveats: >> - some devices still grab a global memory region instead of inheriting >> it from their bus. Seen in the code as #include "exec-memory.h" > > Looks good to me. > > It looks like with this, users of vga_dirty_log_stop > like qxl_write_config can go away because the region can > stay registered with dirty logging enabled? That was already possible with the old API, see [1]. Makes me wonder what will be merged first... Jan [1] http://thread.gmane.org/gmane.comp.emulators.qemu/106150 -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux