From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Liu Ping Fan <pingfank@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] kvm: First step to push iothread lock out of inner run loop
Date: Sat, 23 Jun 2012 11:11:48 +0200 [thread overview]
Message-ID: <4FE58854.2060604@web.de> (raw)
In-Reply-To: <4FE4F8D3.5030203@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 4994 bytes --]
On 2012-06-23 00:59, Anthony Liguori wrote:
> On 06/22/2012 05:45 PM, Jan Kiszka wrote:
>> This sketches a possible path to get rid of the iothread lock on vmexits
>> in KVM mode. On x86, the the in-kernel irqchips has to be used because
>> we otherwise need to synchronize APIC and other per-cpu state accesses
>> that could be changed concurrently. Not yet fully analyzed is the NMI
>> injection path in the absence of an APIC.
>>
>> s390x should be fine without specific locking as their pre/post-run
>> callbacks are empty. Power requires locking for the pre-run callback.
>>
>> This patch is untested, but a similar version was successfully used in
>> a x86 setup with a network I/O path that needed no central iothread
>> locking anymore (required special MMIO exit handling).
>> ---
>> kvm-all.c | 18 ++++++++++++++++--
>> target-i386/kvm.c | 7 +++++++
>> target-ppc/kvm.c | 4 ++++
>> 3 files changed, 27 insertions(+), 2 deletions(-)
>>
>> diff --git a/kvm-all.c b/kvm-all.c
>> index f8e4328..9c3e26f 100644
>> --- a/kvm-all.c
>> +++ b/kvm-all.c
>> @@ -1460,6 +1460,8 @@ int kvm_cpu_exec(CPUArchState *env)
>> return EXCP_HLT;
>> }
>>
>> + qemu_mutex_unlock_iothread();
>> +
>> do {
>> if (env->kvm_vcpu_dirty) {
>> kvm_arch_put_registers(env, KVM_PUT_RUNTIME_STATE);
>> @@ -1476,14 +1478,16 @@ int kvm_cpu_exec(CPUArchState *env)
>> */
>> qemu_cpu_kick_self();
>> }
>> - qemu_mutex_unlock_iothread();
>>
>> run_ret = kvm_vcpu_ioctl(env, KVM_RUN, 0);
>>
>> - qemu_mutex_lock_iothread();
>> kvm_arch_post_run(env, run);
>>
>> + /* TODO: push coalesced mmio flushing to the point where we
>> access
>> + * devices that are using it (currently VGA and E1000). */
>> + qemu_mutex_lock_iothread();
>> kvm_flush_coalesced_mmio_buffer();
>> + qemu_mutex_unlock_iothread();
>>
>> if (run_ret< 0) {
>> if (run_ret == -EINTR || run_ret == -EAGAIN) {
>> @@ -1499,19 +1503,23 @@ int kvm_cpu_exec(CPUArchState *env)
>> switch (run->exit_reason) {
>> case KVM_EXIT_IO:
>> DPRINTF("handle_io\n");
>> + qemu_mutex_lock_iothread();
>> kvm_handle_io(run->io.port,
>> (uint8_t *)run + run->io.data_offset,
>> run->io.direction,
>> run->io.size,
>> run->io.count);
>> + qemu_mutex_unlock_iothread();
>> ret = 0;
>> break;
>> case KVM_EXIT_MMIO:
>> DPRINTF("handle_mmio\n");
>> + qemu_mutex_lock_iothread();
>> cpu_physical_memory_rw(run->mmio.phys_addr,
>> run->mmio.data,
>> run->mmio.len,
>> run->mmio.is_write);
>> + qemu_mutex_unlock_iothread();
>> ret = 0;
>> break;
>> case KVM_EXIT_IRQ_WINDOW_OPEN:
>> @@ -1520,7 +1528,9 @@ int kvm_cpu_exec(CPUArchState *env)
>> break;
>> case KVM_EXIT_SHUTDOWN:
>> DPRINTF("shutdown\n");
>> + qemu_mutex_lock_iothread();
>> qemu_system_reset_request();
>> + qemu_mutex_unlock_iothread();
>> ret = EXCP_INTERRUPT;
>> break;
>> case KVM_EXIT_UNKNOWN:
>> @@ -1533,11 +1543,15 @@ int kvm_cpu_exec(CPUArchState *env)
>> break;
>> default:
>> DPRINTF("kvm_arch_handle_exit\n");
>> + qemu_mutex_lock_iothread();
>> ret = kvm_arch_handle_exit(env, run);
>> + qemu_mutex_unlock_iothread();
>> break;
>> }
>> } while (ret == 0);
>>
>> + qemu_mutex_lock_iothread();
>> +
>> if (ret< 0) {
>> cpu_dump_state(env, stderr, fprintf, CPU_DUMP_CODE);
>> vm_stop(RUN_STATE_INTERNAL_ERROR);
>> diff --git a/target-i386/kvm.c b/target-i386/kvm.c
>> index 0d0d8f6..0ad64d1 100644
>> --- a/target-i386/kvm.c
>> +++ b/target-i386/kvm.c
>> @@ -1631,7 +1631,10 @@ void kvm_arch_pre_run(CPUX86State *env, struct
>> kvm_run *run)
>>
>> /* Inject NMI */
>> if (env->interrupt_request& CPU_INTERRUPT_NMI) {
>
> Strictly speaking, wouldn't we need to use testbit() and setbit()? I
> would expect in the very least a barrier would be needed.
I need to think about this as well. We ignored it so far, just saw it
when hacking up this patch.
>
> Looks pretty nice overall. I'll need to apply and spend some time
> carefully walking through the code.
Without getting the coalesced mmio flushing out of the way, it does not
buy us that much yet. But I have some idea...
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2012-06-23 9:11 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 22:45 [Qemu-devel] [PATCH] kvm: First step to push iothread lock out of inner run loop Jan Kiszka
2012-06-22 22:55 ` Jan Kiszka
2012-06-22 22:55 ` [Qemu-devel] " Jan Kiszka
2012-06-23 0:22 ` Marcelo Tosatti
2012-06-23 0:22 ` [Qemu-devel] " Marcelo Tosatti
2012-06-23 9:06 ` Marcelo Tosatti
2012-06-23 9:06 ` [Qemu-devel] " Marcelo Tosatti
2012-06-23 11:45 ` Jan Kiszka
2012-06-23 11:45 ` [Qemu-devel] " Jan Kiszka
2012-06-24 8:49 ` Avi Kivity
2012-06-24 8:49 ` [Qemu-devel] " Avi Kivity
2012-06-24 14:08 ` Jan Kiszka
2012-06-24 14:08 ` Jan Kiszka
2012-06-24 14:31 ` Avi Kivity
2012-06-24 14:31 ` Avi Kivity
2012-07-06 17:16 ` Jan Kiszka
2012-07-06 17:16 ` [Qemu-devel] " Jan Kiszka
2012-07-06 18:06 ` Jan Kiszka
2012-07-06 18:06 ` [Qemu-devel] " Jan Kiszka
2012-07-08 7:49 ` Avi Kivity
2012-07-08 7:49 ` [Qemu-devel] " Avi Kivity
2012-06-24 13:34 ` liu ping fan
2012-06-24 13:34 ` [Qemu-devel] " liu ping fan
2012-06-24 14:08 ` Jan Kiszka
2012-06-24 14:08 ` [Qemu-devel] " Jan Kiszka
2012-06-24 14:35 ` Avi Kivity
2012-06-24 14:35 ` [Qemu-devel] " Avi Kivity
2012-06-24 14:40 ` Jan Kiszka
2012-06-24 14:40 ` [Qemu-devel] " Jan Kiszka
2012-06-24 14:46 ` Avi Kivity
2012-06-24 14:46 ` [Qemu-devel] " Avi Kivity
2012-06-24 14:51 ` Jan Kiszka
2012-06-24 14:51 ` [Qemu-devel] " Jan Kiszka
2012-06-24 14:56 ` Avi Kivity
2012-06-24 14:56 ` [Qemu-devel] " Avi Kivity
2012-06-24 14:58 ` Jan Kiszka
2012-06-24 14:58 ` [Qemu-devel] " Jan Kiszka
2012-06-24 14:59 ` Avi Kivity
2012-06-24 14:59 ` [Qemu-devel] " Avi Kivity
2012-06-23 9:22 ` Jan Kiszka
2012-06-23 9:22 ` [Qemu-devel] " Jan Kiszka
2012-06-28 1:11 ` Marcelo Tosatti
2012-06-26 19:34 ` Marcelo Tosatti
2012-06-27 7:39 ` Stefan Hajnoczi
2012-06-27 7:41 ` [Qemu-devel] " Stefan Hajnoczi
2012-06-27 11:09 ` Marcelo Tosatti
2012-06-27 11:19 ` [Qemu-devel] " Marcelo Tosatti
2012-06-28 8:45 ` Stefan Hajnoczi
2012-06-27 7:54 ` Avi Kivity
2012-06-27 14:36 ` Jan Kiszka
2012-06-28 14:10 ` [Qemu-devel] " Anthony Liguori
2012-06-28 15:12 ` Avi Kivity
2012-06-29 1:29 ` Marcelo Tosatti
2012-06-29 1:45 ` [Qemu-devel] " Marcelo Tosatti
2012-06-22 22:59 ` Anthony Liguori
2012-06-23 9:11 ` Jan Kiszka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE58854.2060604@web.de \
--to=jan.kiszka@web.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.