Il 23/05/2013 09:09, liu ping fan ha scritto:
>> > void address_space_rw(AddressSpace *as, hwaddr addr, uint8_t *buf,
>> > int len, bool is_write)
>> > {
>> > - AddressSpaceDispatch *d = as->dispatch;
>> > - int l;
>> > + hwaddr l;
>> > uint8_t *ptr;
>> > uint32_t val;
>> > - hwaddr page;
>> > + hwaddr addr1;
>> > MemoryRegionSection *section;
>> >
>> > while (len > 0) {
>> > - page = addr & TARGET_PAGE_MASK;
>> > - l = (page + TARGET_PAGE_SIZE) - addr;
>> > - if (l > len)
>> > - l = len;
>> > - section = phys_page_find(d, page >> TARGET_PAGE_BITS);
>> > + l = len;
>> > + section = address_space_translate(as, addr, &addr1, &l, is_write);
>> >
> Jan's "Rework sub-page handling" patch broke the tlb_set_page
> (anything else?) But I think we still need a function based on
> address_space_translate to wrap the subpage logic inside and ease the
> incoming RCU style.
The idea is that address_space_translate gets a ref to the MemoryRegion,
and the ref is then released by the caller of address_space_translate.
That means that the actual memory accesses can run outside the RCU
critical section.
But I'm not sure how that is related to subpage logic. Subpages are
simply MemoryRegions that only exist in the phys page map, rather than
within an AddressSpace. Their destruction will be delayed anyway by
doing call_rcu on the old phys page map.
Paolo
