On 05/18/2011 02:40 PM, Jan Kiszka wrote:
On 2011-05-18 15:12, Avi Kivity wrote:
void cpu_register_memory_region(MemoryRegion *mr, target_phys_addr_t addr);
OK, let's allow overlapping, but make it explicit:
void cpu_register_memory_region_overlap(MemoryRegion *mr,
target_phys_addr_t addr,
int priority);
The device doesn't actually know how overlapping is handled. This is
based on the bus hierarchy.
Regards,
Anthony Liguori
We need that ordering, so we need an interface. Regions registered via
cpu_register_memory_region must not overlap with existing one or we will
throw an hwerror. And they shall get a low default priority.
Jan
