Re: [Qemu-devel] [PATCH for-2.4 0/8] memory: enable unlocked PIO/MMIO in KVM

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2015-03-18 14:21, Paolo Bonzini wrote:
> And here we are...  These are the changes required to make the BQL
> optional for memory access, and use that support in KVM.  For now,
> only one device model is changed to do unlocked accesses.
> 
> Please review!
> 
> Jan Kiszka (4):
>   memory: Add global-locking property to memory regions
>   memory: Provide address_space_rw_unlocked
>   kvm: First step to push iothread lock out of inner run loop
>   kvm: Switch to unlocked PIO
> 
> Paolo Bonzini (4):
>   exec: move rcu_read_lock/unlock to address_space_translate callers
>   exec: mark unassigned_io_ops as unlocked
>   acpi: mark PMTIMER as unlocked
>   kvm: Switch to unlocked MMIO
> 
>  exec.c                | 75 ++++++++++++++++++++++++++++++++++++++++++++++-----
>  hw/acpi/core.c        |  1 +
>  hw/vfio/common.c      |  7 +++--
>  include/exec/memory.h | 48 ++++++++++++++++++++++++++++++++-
>  kvm-all.c             | 23 ++++++++++------
>  memory.c              | 17 +++++++-----
>  target-i386/kvm.c     | 18 +++++++++++++
>  target-mips/kvm.c     |  4 +++
>  target-ppc/kvm.c      |  4 +++
>  translate-all.c       |  3 +++
>  10 files changed, 177 insertions(+), 23 deletions(-)
> 

Just in time: I'm planning to rebase our queue soon, specifically to
benefit from RCU support. Will let you know if it works on top of this
series.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux