On 07/19/2011 04:56 PM, 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?
Yes. You set the property once on the framebuffer, and it and all aliases are tracked whenever they or a subregion are exposed.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
