Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2419968pxb; Sun, 31 Oct 2021 15:36:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyUH5JZ0TlEoivEWhrsZIVicehpohdWOixBu0ZDF56YUFn0Qhn3YnPQwo/+r1KRCWBIg6wC X-Received: by 2002:a17:906:d1d1:: with SMTP id bs17mr30584138ejb.198.1635719789174; Sun, 31 Oct 2021 15:36:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635719789; cv=none; d=google.com; s=arc-20160816; b=rmRy5lhcDIOgRcm/BHWxxUj3S5HnUAtvOqhyNqncjzxkI2SIHerkBXhTZUR1td0XKG xn7N2YFaXgiFJsDHWoWjw54ZioibQDmb+QdjF7Re691yxvOexdhEAPnj8t25cQL6sbFH AZoLY1jTPYCgIHbTSts1s2O7K0wlhvjocA48IGqNd3h8PRI2XvWzp1gxPinWbBTScpWY VDqIcto+yUH2HAdx11PrSSLVrdFlVaQBAZLproN4TOhdPHk+L8UAfjmwWEoJYQJF2kfx T3kxAvTCX+waxL73v6FPEahEEPgBQvUyedrib6XqHdoh+/JodiaU8MPOVAI7gHPKWj9N Yyqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=c8n/xhA0zJkzOmAPtQLtzvCuXP3Hx32iHbMD3xWco1s=; b=Ri/3l7Q1y5FBmK8PLMdKgsH1VYJKKiVNgamE771vApD77K2xUHOeebzv7GFx0buev4 dnMuJqEdvghRQsTrOKCBKDXyS0KjyDCW0er3jhkjQtcENO37i6dHYyuSbXoY7PvyK2+1 aFJtS0Rn5ZZJmmDcSe2qEafbGfPI8uGVzLv/72TwUi5iV1krCn5WNddyB5HiA9Fl9mm+ AdUzw8L61SxCszYw7Ueo5uWPyAVGeDNj8j94CwwBuKjFTf6H1Zw0qJLErHD+vi5meYm9 6PzQ7BXH3LYIysXQGRrfi8gL4rgivkxq9sIZfCs7a7Wqdf0jNSGyDpRZ9gqHnt1PuFm/ hktQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=AxOlOtdC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e10si28196118edz.136.2021.10.31.15.36.04; Sun, 31 Oct 2021 15:36:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=AxOlOtdC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230291AbhJaWgx (ORCPT + 99 others); Sun, 31 Oct 2021 18:36:53 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:36799 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230125AbhJaWgq (ORCPT ); Sun, 31 Oct 2021 18:36:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1635719653; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c8n/xhA0zJkzOmAPtQLtzvCuXP3Hx32iHbMD3xWco1s=; b=AxOlOtdClkcei5Sn80mjtZM4CWZVHeJLuLtDHNmbhmzy6Ku/DTlBlfLutQtoz0RbxJ3zZB 27nRT0goSAEjZNCrZZZ5CzZ2pXRj5YOaSwsNZrSMRXnOxq6cQ4ziHYtidMCOJt6TCS1UVM 07FfSP7rsNoXnMsUYEHTiIi07Gbyrr4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-492-IUrqtT12PAernuCzxMBHeQ-1; Sun, 31 Oct 2021 18:34:08 -0400 X-MC-Unique: IUrqtT12PAernuCzxMBHeQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E3A2080A5C0; Sun, 31 Oct 2021 22:34:04 +0000 (UTC) Received: from starship (unknown [10.40.194.243]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4CB8619C59; Sun, 31 Oct 2021 22:33:42 +0000 (UTC) Message-ID: Subject: Re: [PATCH v2 43/43] KVM: VMX: Don't do full kick when handling posted interrupt wakeup From: Maxim Levitsky To: Paolo Bonzini , Sean Christopherson , Marc Zyngier , Huacai Chen , Aleksandar Markovic , Paul Mackerras , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Christian Borntraeger , Janosch Frank Cc: James Morse , Alexandru Elisei , Suzuki K Poulose , Atish Patra , David Hildenbrand , Cornelia Huck , Claudio Imbrenda , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-mips@vger.kernel.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, David Matlack , Oliver Upton , Jing Zhang Date: Mon, 01 Nov 2021 00:33:40 +0200 In-Reply-To: <01b5edae-aaa9-e96d-daaa-197c0c3a0431@redhat.com> References: <20211009021236.4122790-1-seanjc@google.com> <20211009021236.4122790-44-seanjc@google.com> <01b5edae-aaa9-e96d-daaa-197c0c3a0431@redhat.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2021-10-25 at 16:16 +0200, Paolo Bonzini wrote: > On 09/10/21 04:12, Sean Christopherson wrote: > > When waking vCPUs in the posted interrupt wakeup handling, do exactly > > that and no more. There is no need to kick the vCPU as the wakeup > > handler just need to get the vCPU task running, and if it's in the guest > > then it's definitely running. > > And more important, the transition from blocking to running will have > gone through sync_pir_to_irr, thus checking ON and manually moving the > vector from PIR to RVI. > > Paolo > I also think so, and maybe this can be added to the commit message. Anyway, last one for the series :) Reviewed-by: Maxim Levitsky Best regards, Maxim Levitsky