Received: by 10.223.176.5 with SMTP id f5csp1845673wra; Thu, 8 Feb 2018 04:32:57 -0800 (PST) X-Google-Smtp-Source: AH8x224Qh9z7lmiABz99UDcddlb4lAcSvmJJv+gkjj1R3Edp0rLmtaIugG4foA3+upTSkSZoMori X-Received: by 10.101.67.71 with SMTP id k7mr426422pgq.136.1518093177559; Thu, 08 Feb 2018 04:32:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518093177; cv=none; d=google.com; s=arc-20160816; b=gO1IFKGaATSR7dfsYCUaCPthQ8Mtkit0X7RxBdqlBJv6Apu9+mk8FQeX6y0ZPhwBY6 LWzRJW36sA2FjDMm0iF4gBQmL/feeFJHmzRnRYKTL1midAUgNhwT5GsZyS4P8U7v2/ew MqjCFEHCimSFiprNPrmoUqC86qoH6hGswUYaVFF0XYRKzXocVFJ/WBM/lfbVGMuwShT3 /dkpEFj3lO237FieALjZFN2r12jbF/lDeZNX5UKk2CWXYitc5uLTQAIhq7lUmaGZS6Lh 7AUtzDKcu5GGPdKc3Xz7iKAAfeOquCyJOZYTDcPk9SazrF0ugJf0dEQLMpdpDvppofI4 DLZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=1zFCTp/RKN/Ds0HxiYFlEVczao9Dh8kDf5EzQove/rA=; b=UHUHlYyArbYFrdMaLDKTGj0Jc4uML00K/8NFCatUZ3k9s9d76geXOnjSGHQ5vfawai OnGMSzn+VGbFXGvrra7jMtU3bUNh+v5Sm52IZTFGldcLIKnAaoeTIQ0ijtsB1/w5FZvP aY6m/UOIl0jAozWl/BYKemyPS7E74qBduT9Ai8yUL8OJPn7+vVP5pBPO2WgkbXnLrkqC rk8SPb4zDVWe2dRL07uVibFAbZsDeRoVC/oYdoBVtRU9UHupA7z4Z/vGez6s9TiSZeDJ JC40wLM5ZknF9RcWsc8gMDDDbc0w1H4HD09dlkqJ2daW+OIRzO4spEAYBDgiIr6mMS3h WqOg== 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 bg8-v6si2704389plb.748.2018.02.08.04.32.43; Thu, 08 Feb 2018 04:32:57 -0800 (PST) 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 S1751998AbeBHMcD (ORCPT + 99 others); Thu, 8 Feb 2018 07:32:03 -0500 Received: from mga17.intel.com ([192.55.52.151]:45883 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751725AbeBHMcB (ORCPT ); Thu, 8 Feb 2018 07:32:01 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Feb 2018 04:32:00 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,478,1511856000"; d="scan'208";a="29866918" Received: from skl-4s-chao.sh.intel.com ([10.239.48.67]) by orsmga001.jf.intel.com with ESMTP; 08 Feb 2018 04:31:58 -0800 Date: Thu, 8 Feb 2018 19:20:28 +0800 From: Chao Gao To: Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , Radim =?utf-8?B?S3LEjW3DocWZ?= , Liran Alon Subject: Re: [PATCH] x86/kvm/vmx: Don't halt vcpu when L1 is injecting events to L2 Message-ID: <20180208112027.GA116170@skl-4s-chao.sh.intel.com> References: <1518066816-7197-1-git-send-email-chao.gao@intel.com> <7de4e758-08cc-2c45-b0aa-dfe28dfef398@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7de4e758-08cc-2c45-b0aa-dfe28dfef398@redhat.com> User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 08, 2018 at 11:29:49AM +0100, Paolo Bonzini wrote: >On 08/02/2018 06:13, Chao Gao wrote: >> Although L2 is in halt state, it will be in the active state after >> VM entry if the VM entry is vectoring. Halting the vcpu here means >> the event won't be injected to L2 and this decision isn't reported >> to L1. Thus L0 drops an event that should be injected to L2. >> >> Because virtual interrupt delivery may wake L2 vcpu, if VID is enabled, >> do the same thing -- don't halt L2. > >This second part seems wrong to me, or at least overly general. Perhaps >you mean if RVI>0? Yes. It is a little general. How about this patch: -- 8> -- Subject: [PATCH] x86/kvm/vmx: Don't halt vcpu when L1 is injecting events to L2 Although L2 is in halt state, it will be in the active state after VM entry if the VM entry is vectoring. Halting the vcpu here means the event won't be injected to L2 and this decision isn't reported to L1. Thus L0 drops an event that should be injected to L2. Because virtual interrupt delivery may wake L2 vcpu, if VID is enabled and RVI > 0, do the same thing -- don't halt L2. Signed-off-by: Chao Gao --- arch/x86/kvm/vmx.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index bb5b488..fa889c8 100644 --- a/arch/x86/kvm/vmx.c +++ b/arch/x86/kvm/vmx.c @@ -10985,7 +10985,13 @@ static int nested_vmx_run(struct kvm_vcpu *vcpu, bool launch) if (ret) return ret; - if (vmcs12->guest_activity_state == GUEST_ACTIVITY_HLT) + /* + * If we're entering a halted L2 vcpu and the L2 vcpu won't be woken + * by event injection or VID, halt vcpu for optimization. + */ + if ((vmcs12->guest_activity_state == GUEST_ACTIVITY_HLT) && + !(vmcs12->vm_entry_intr_info_field & VECTORING_INFO_VALID_MASK) && + !(nested_cpu_has_vid(vmcs12) && (vmcs12->guest_intr_status & 0xff))) return kvm_vcpu_halt(vcpu); vmx->nested.nested_run_pending = 1; -- > >Thanks, > >Paolo > >> Signed-off-by: Chao Gao >> --- >> arch/x86/kvm/vmx.c | 10 ++++++++-- >> 1 file changed, 8 insertions(+), 2 deletions(-) >> >> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c >> index bb5b488..e1fe4e4 100644 >> --- a/arch/x86/kvm/vmx.c >> +++ b/arch/x86/kvm/vmx.c >> @@ -10985,8 +10985,14 @@ static int nested_vmx_run(struct kvm_vcpu *vcpu, bool launch) >> if (ret) >> return ret; >> >> - if (vmcs12->guest_activity_state == GUEST_ACTIVITY_HLT) >> - return kvm_vcpu_halt(vcpu); >> + if (vmcs12->guest_activity_state == GUEST_ACTIVITY_HLT) { >> + u32 intr_info = vmcs_read32(VM_ENTRY_INTR_INFO_FIELD); >> + u32 exec_control = vmcs_read32(SECONDARY_VM_EXEC_CONTROL); >> + >> + if (!(intr_info & VECTORING_INFO_VALID_MASK) && >> + !(exec_control & SECONDARY_EXEC_VIRTUAL_INTR_DELIVERY)) >> + return kvm_vcpu_halt(vcpu); >> + } > >> vmx->nested.nested_run_pending = 1; >> >> >