Re: [RFC v4 00/58] Memory API

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
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


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux