Paolo,

Am 03.02.2014 10:44, schrieb Edgar E. Iglesias:
> Edgar E. Iglesias (22):
>   exec: Make tb_invalidate_phys_addr input an AS
>   exec: Make iotlb_to_region input an AS
>   exec: Always initialize MemorySection address spaces
>   exec: Make memory_region_section_get_iotlb use section AS
>   memory: Add MemoryListener to typedefs.h

I've been waiting on your review of this series since CPU changes start
only with the next patch and I consider most of them a "memory" topic.

Do you intend to review them or should I go ahead and queue these on
qom-cpu if they compile and don't obviously break things?

Thanks in advance,

Andreas

>   cpu: Add per-cpu address space
>   exec: On AS changes, only flush affected CPU TLBs
>   exec: Make ldl_*_phys input an AddressSpace
>   exec: Make ldq/ldub_*_phys input an AddressSpace
>   exec: Make lduw_*_phys input an AddressSpace
>   exec: Make stq_*_phys input an AddressSpace
>   exec: Make stl_*_phys input an AddressSpace
>   exec: Make stl_phys_notdirty input an AddressSpace
>   exec: Make stw_*_phys input an AddressSpace
>   exec: Make stb_phys input an AddressSpace
>   exec: Make cpu_physical_memory_write_rom input an AS
>   exec: Make cpu_memory_rw_debug use the CPUs AS
>   memory: Add address_space_find_by_name()
>   qdev: Add qdev property type for AddressSpaces
>   cpu: Add address-space property
>   petalogix-ml605: Create the CPU with object_new()
>   petalogix-ml605: Make the LMB visible only to the CPU

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

Reply via email to