On 22/01/19 17:36, Peter Maydell wrote:
>> +void memory_region_flush_rom_device(MemoryRegion *mr, hwaddr addr, hwaddr
>> size)
>> +{
>> + /* In principle this function would work on other memory region types
>> too,
>> + * but the ROM device use case is the only one where this operation is
>> + * necessary. Other memory regions should use the
>> + * address_space_read/write() APIs.
>> + */
>> + assert(memory_region_is_romd(mr));
>> +
>> + invalidate_and_set_dirty(mr, addr, size);
>> +}
>> +
>> static int memory_access_size(MemoryRegion *mr, unsigned l, hwaddr addr)
>> {
>> unsigned access_size_max = mr->ops->valid.max_access_size;
> API and implementation make sense to me, but better that Paolo reviews
> this I think. I guess we should add calls to this to the pflash device
> models too...
Yes, I agree. The implementation makes sense, though maybe we could
just rename invalidate_and_set_dirty to
memory_region_invalidate_and_set_dirty. Whatever you guys prefer.
Paolo
