[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH for-2.4 0/8] memory: enable unlocked PIO/MMIO in
|
From: |
Paolo Bonzini |
|
Subject: |
Re: [Qemu-devel] [PATCH for-2.4 0/8] memory: enable unlocked PIO/MMIO in KVM |
|
Date: |
Wed, 18 Mar 2015 15:52:30 +0100 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 |
On 18/03/2015 15:33, Jan Kiszka wrote:
> 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.
Great. FWIW, this is the most similar version to the one we played with
in 2013.
I have an alternative one that keeps the single address_space_rw API,
and checks if you have the iothread mutex using thread-local storage.
The reason for that is that I would have to introduce
address_space_map/unmap_unlocked too, which I didn't really like. Also,
in the not-so-long term we want the same code (e.g. SCSI layer) to run
in both locked and unlocked mode.
What do you think?
Paolo
- [Qemu-devel] [PATCH 3/8] memory: Provide address_space_rw_unlocked, (continued)
- [Qemu-devel] [PATCH 3/8] memory: Provide address_space_rw_unlocked, Paolo Bonzini, 2015/03/18
- [Qemu-devel] [PATCH 2/8] exec: move rcu_read_lock/unlock to address_space_translate callers, Paolo Bonzini, 2015/03/18
- [Qemu-devel] [PATCH 4/8] kvm: First step to push iothread lock out of inner run loop, Paolo Bonzini, 2015/03/18
- [Qemu-devel] [PATCH 6/8] exec: mark unassigned_io_ops as unlocked, Paolo Bonzini, 2015/03/18
- [Qemu-devel] [PATCH 7/8] acpi: mark PMTIMER as unlocked, Paolo Bonzini, 2015/03/18
- [Qemu-devel] [PATCH 5/8] kvm: Switch to unlocked PIO, Paolo Bonzini, 2015/03/18
- [Qemu-devel] [PATCH 8/8] kvm: Switch to unlocked MMIO, Paolo Bonzini, 2015/03/18
- Re: [Qemu-devel] [PATCH for-2.4 0/8] memory: enable unlocked PIO/MMIO in KVM, Jan Kiszka, 2015/03/18
- Re: [Qemu-devel] [PATCH for-2.4 0/8] memory: enable unlocked PIO/MMIO in KVM,
Paolo Bonzini <=