Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp123953ybi; Thu, 1 Aug 2019 15:54:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqynzmvzGF7D6DT8YZzXjPmrprsTirrdoJaYUDlTRtjnUl4azxcegl427YOnT1Hh6sjCy8z9 X-Received: by 2002:a17:90a:cb18:: with SMTP id z24mr1128776pjt.108.1564700096974; Thu, 01 Aug 2019 15:54:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564700096; cv=none; d=google.com; s=arc-20160816; b=m4nsuHtAQ/VCqgCkkYxLgo1FXyRH86Zdb8br92DUkTQpgBYPFGyHnrdeTQi8+unhv9 vIieWsng64pO1ReMb8E2Eauz38zWz8Mg2QXWEG/GT5PE8RtrHXkgAVvb0DpbLD/tKSGy 2GDXziWaNHKxnQpLbewieQmchwnEP+55IMvwToIn5fTBUJnHBKqKhxOCDr/BRS3bnEms YMbPfBV+w//BLNUHToucRl4v8VnbzfJwagypcDH6juRIYgtuppJ7zWgr1I1lxfuyxy4/ 0K3KnFG6gtce/uuXlHy2Y2P9CElCPNg3G73tQwgz/i0ooLJsPa304c7Oiy55dr7NKevw fFHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=ZsXmUrJnantZ/7L2BqkX1UBki3pmGd2PRL9+U69t9Jo=; b=tYZpqmfQhrfto1RkZNdhEnbHMcydyDzxnzt6gdETa9QLQIUNnmY3Yn1HbLeLuCr9e0 NaIbgTAYgRnJqvGrF7oL0VyolLNQpA6Lq8yRMHGyTtjGJTLPy5iPs1S9lPtkT4UocUgU tUD9z2fQ9lj8Xt70K3Q7MS/8Ds9roBo2Pa/4/MAK02miN1ziKxwx0H8/VRtAVuyzZHW7 Ze//oP4bM0uKwjqKETsievRk9YbAMMvThC88ktRP07Y5JrRmBF8x9QG+Rmn9ymoYA+P6 abmErwdXnGLyAKq5e9Q/2d6YOwwXVE4fONxkfwrQOLzMS60pYW8yI+pZbcu2ah6v5Erv P1NQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m12si5183102pjq.60.2019.08.01.15.54.41; Thu, 01 Aug 2019 15:54:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731869AbfHASfG (ORCPT + 99 others); Thu, 1 Aug 2019 14:35:06 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:37603 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727218AbfHASfF (ORCPT ); Thu, 1 Aug 2019 14:35:05 -0400 Received: from pd9ef1cb8.dip0.t-ipconnect.de ([217.239.28.184] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1htFug-0007CB-NP; Thu, 01 Aug 2019 20:34:54 +0200 Date: Thu, 1 Aug 2019 20:34:53 +0200 (CEST) From: Thomas Gleixner To: Oleg Nesterov cc: LKML , x86@kernel.org, Peter Zijlstra , Ingo Molnar , Sebastian Siewior , Anna-Maria Gleixner , Steven Rostedt , Julia Cartwright , Paul McKenney , Frederic Weisbecker , kvm@vger.kernel.org, Radim Krcmar , Paolo Bonzini , John Stultz , Andy Lutomirski , "Paul E. McKenney" Subject: Re: [patch 2/5] x86/kvm: Handle task_work on VMENTER/EXIT In-Reply-To: <20190801162451.GE31538@redhat.com> Message-ID: References: <20190801143250.370326052@linutronix.de> <20190801143657.887648487@linutronix.de> <20190801162451.GE31538@redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 1 Aug 2019, Oleg Nesterov wrote: > On 08/01, Thomas Gleixner wrote: > > > > @@ -8172,6 +8174,10 @@ static int vcpu_run(struct kvm_vcpu *vcp > > ++vcpu->stat.signal_exits; > > break; > > } > > + > > + if (notify_resume_pending()) > > + tracehook_handle_notify_resume(); > > shouldn't you drop kvm->srcu before tracehook_handle_notify_resume() ? > > I don't understand this code at all, but vcpu_run() does this even before > cond_resched(). Yeah, I noticed that it's dropped around cond_resched(). My understanding is that for voluntary giving up the CPU via cond_resched() it needs to be dropped. For involuntary preemption (CONFIG_PREEMPT=y) it's not required as the whole code section after preempt_enable() is fully preemptible. Now the 1Mio$ question is whether any of the notify functions invokes cond_resched() and whether that really matters. Paolo? Thanks, tglx