From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC v4 00/58] Memory API Date: Wed, 20 Jul 2011 19:53:45 +0300 Message-ID: <4E270819.20701@redhat.com> References: <1310901265-32051-1-git-send-email-avi@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: qemu-devel@nongnu.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:8497 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751986Ab1GTQxu (ORCPT ); Wed, 20 Jul 2011 12:53:50 -0400 In-Reply-To: <1310901265-32051-1-git-send-email-avi@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/17/2011 02:13 PM, 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" Still available from git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory-region chop off the top two commits to avoid lots of debugging info. -- error compiling committee.c: too many arguments to function