From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751850AbdI1HWL (ORCPT ); Thu, 28 Sep 2017 03:22:11 -0400 Received: from mail-wm0-f65.google.com ([74.125.82.65]:35602 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750794AbdI1HWJ (ORCPT ); Thu, 28 Sep 2017 03:22:09 -0400 X-Google-Smtp-Source: AOwi7QDDO73vYnimjviqbv4wjiTBorf87z9NsqxIdutZNZ+aEPoOLO5/d3mDJQacrNLtyXQzzw7I5w== Subject: Re: [patch 3/3] x86: kvm guest side support for KVM_HC_RT_PRIO hypercall\ To: Marcelo Tosatti Cc: Peter Zijlstra , Konrad Rzeszutek Wilk , mingo@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner References: <20170922123305.GB29608@amt.cnet> <20170922125556.cyzybj6c7jqypbmo@hirez.programming.kicks-ass.net> <951aaa3f-b20d-6f67-9454-f193f4445fc7@redhat.com> <20170923134114.qdfdegrd6afqrkut@hirez.programming.kicks-ass.net> <855950672.7912001.1506258344142.JavaMail.zimbra@redhat.com> <20170925025751.GB30813@amt.cnet> <20170925091316.bnwpiscs2bvpdxk5@hirez.programming.kicks-ass.net> <00ff8cbf-4e41-a950-568c-3bd95e155d4b@redhat.com> <20170926224925.GA9119@amt.cnet> <6f4afefd-8726-13ff-371e-0d3896b4cf6a@redhat.com> <20170928004452.GA30040@amt.cnet> From: Paolo Bonzini Message-ID: <10635834-459a-9ec1-624d-febd6b5af243@redhat.com> Date: Thu, 28 Sep 2017 09:22:02 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20170928004452.GA30040@amt.cnet> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28/09/2017 02:44, Marcelo Tosatti wrote: >> Again: if you have many interruptions, it's not a flaw in KVM or QEMU's >> design, it's just that someone is doing something stupid. It could be >> the guest (e.g. unnecessary devices or daemons as in the example above), >> QEMU (e.g. the RTC emulation used to trigger QEMU timers twice a second >> just to increment the clock), or the management (e.g. polling "is the VM >> running" 50 times per second). But it can and must be fixed. > > No, i mean you can run anything in VCPU-0 (it is valid to do that). > And that "anything" can generate 1 interrupt per second, 1000 or 10.000 > interrupts per second. Which are all valid things to be done. > > "I can't run a kernel compilation on VCPU-0 because that will impact > latency on the realtime VCPU-1" is not acceptable. That shouldn't happen. Sources of frequent interruptions have all been fixed or moved outside the main thread. If there are more left, report the bug and we'll see how to fix it in userspace. Paolo