On Fri, May 16, 2014 at 11:54 AM, Peter Crosthwaite <peter.crosthwa...@xilinx.com> wrote: > QOM propertyify the .may-overlap and .priority fields. The setters > will re-add the memory as a subregion if needed (i.e. the values change > when the memory region is already contained). > > Signed-off-by: Peter Crosthwaite <peter.crosthwa...@xilinx.com> > --- > > include/exec/memory.h | 2 +- > memory.c | 58 > ++++++++++++++++++++++++++++++++++++++++++++++++++- > 2 files changed, 58 insertions(+), 2 deletions(-) > > diff --git a/include/exec/memory.h b/include/exec/memory.h > index 2bb074f..1f12c15 100644 > --- a/include/exec/memory.h > +++ b/include/exec/memory.h > @@ -158,7 +158,7 @@ struct MemoryRegion { > bool flush_coalesced_mmio; > MemoryRegion *alias; > hwaddr alias_offset; > - int priority; > + uint32_t priority;
It appears as if -ve memory region priorities are valid and work. Will preserve this and change to this type to int32_t. Regards, Peter > bool may_overlap; > QTAILQ_HEAD(subregions, MemoryRegion) subregions; > QTAILQ_ENTRY(MemoryRegion) subregions_link; > diff --git a/memory.c b/memory.c > index 9b9cfad..e1236c1 100644 > --- a/memory.c > +++ b/memory.c > @@ -859,7 +859,6 @@ void memory_region_init(MemoryRegion *mr, > mr->name = g_strdup(name); > } > > static uint64_t unassigned_mem_read(void *opaque, hwaddr addr, > -- > 1.9.3.1.ga73a6ad >