From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: qemu polling KVM_IRQ_LINE_STATUS when stopped Date: Wed, 18 Oct 2017 21:24:33 +0200 Message-ID: <3d37ef15-932a-1492-3068-9ef0b8cd5794@redhat.com> References: <87a80pihlz.fsf@linux.intel.com> <1ffc9cf7-a81c-6eeb-4823-c6e0ef53d3af@redhat.com> <20171018174946.GU5109@tassilo.jf.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: kvm@vger.kernel.org To: Andi Kleen Return-path: Received: from mx1.redhat.com ([209.132.183.28]:48752 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750880AbdJRTYg (ORCPT ); Wed, 18 Oct 2017 15:24:36 -0400 In-Reply-To: <20171018174946.GU5109@tassilo.jf.intel.com> Content-Language: en-US Sender: kvm-owner@vger.kernel.org List-ID: On 18/10/2017 19:49, Andi Kleen wrote: > > The ioctl appears to be the PIC timer > > - 6.36% __GI___ioctl ▒ > kvm_vm_ioctl ▒ > kvm_set_irq ▒ > kvm_pic_set_irq PIC is the interrupt controller, why do you say the timer? What is the QEMU side of the call stack? > - 2.83% libglib-2.0.so.0.5200.3 [.] g_main_context_check ▒ > - 2.81% g_main_context_check ▒ > - 2.60% main_loop_wait ▒ > main ▒ > __libc_start_main ▒ > _start > > And some AIO is going on, not sure what triggers that. > > 1.96% aio_ctx_check ▒ "check" is just "do I have something to do?" so it runs on every iteration. Paolo