[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 3/9] memory: Add global-locking property to memo
From: |
Fam Zheng |
Subject: |
Re: [Qemu-devel] [PATCH 3/9] memory: Add global-locking property to memory regions |
Date: |
Thu, 25 Jun 2015 18:59:59 +0800 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Thu, 06/25 09:46, Paolo Bonzini wrote:
>
>
> On 25/06/2015 05:44, Fam Zheng wrote:
> >> > + * memory_region_clear_global_locking: Declares that access processing
> >> > does
> >> > + * not depend on the QEMU global
> >> > lock.
> >> > + *
> >> > + * By clearing this property, accesses to the memory region will be
> >> > processed
> > Inconsistent with singlar form (access) in the previous one. Otherwise,
>
> I think this is correct English actually. "Access processing" in the
> first line cannot use a plural because it behaves as a single word.
> Let's ask a native speaker. :)
I meant the above "When this is invoked, access to this memory regions will be
processed..." compared to this "accesses to the memory region".
Fam
[Qemu-devel] [PATCH 4/9] exec: pull qemu_flush_coalesced_mmio_buffer() into address_space_rw/ld*/st*, Paolo Bonzini, 2015/06/24
[Qemu-devel] [PATCH 1/9] main-loop: use qemu_mutex_lock_iothread consistently, Paolo Bonzini, 2015/06/24
[Qemu-devel] [PATCH 2/9] main-loop: introduce qemu_mutex_iothread_locked, Paolo Bonzini, 2015/06/24
[Qemu-devel] [PATCH 5/9] memory: let address_space_rw/ld*/st* run outside the BQL, Paolo Bonzini, 2015/06/24