From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 63056C433F5 for ; Tue, 30 Nov 2021 21:09:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343957AbhK3VNQ (ORCPT ); Tue, 30 Nov 2021 16:13:16 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:57686 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343965AbhK3VMw (ORCPT ); Tue, 30 Nov 2021 16:12:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1638306572; 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=vRB0jIIZXNaYYuntWB3mFkvxtYXPPauos8UWrZOu2Ig=; b=g+w18r0l0Mjp+j1TuvasrzOun5T8F2oEQCR+0z7jESFJ3mG8fDV/G4yG0kncRoQX8EK1Bs pUBPtN8gluK7pBAY635X9Hgf03ck4tG5h0VjYTPF50xUO9Zq32an2mUsrlh2ONu+KSZekh QwbBTe84xRePHIL87Ih+FlLjkeaz8hw= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-521-Cy-L5SpqOxWp9ZVsNGWBlA-1; Tue, 30 Nov 2021 16:09:28 -0500 X-MC-Unique: Cy-L5SpqOxWp9ZVsNGWBlA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 950E110168DB; Tue, 30 Nov 2021 21:09:27 +0000 (UTC) Received: from starship (unknown [10.40.192.24]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0C52460C0F; Tue, 30 Nov 2021 21:09:25 +0000 (UTC) Message-ID: <160133d3f2760d636414ff067dd4b44b6e311c6f.camel@redhat.com> Subject: Re: [PATCH] KVM: VMX: clear vmx_x86_ops.sync_pir_to_irr if APICv is disabled From: Maxim Levitsky To: Sean Christopherson , Paolo Bonzini Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Date: Tue, 30 Nov 2021 23:09:24 +0200 In-Reply-To: References: <20211130123746.293379-2-pbonzini@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.79 on 10.5.11.12 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2021-11-30 at 20:32 +0000, Sean Christopherson wrote: > On Tue, Nov 30, 2021, Paolo Bonzini wrote: > > There is nothing to synchronize if APICv is disabled, since neither > > other vCPUs nor assigned devices can set PIR.ON. > > > > Signed-off-by: Paolo Bonzini > > --- > > Reviewed-by: Sean Christopherson > Reviewed-by: Maxim Levitsky Best regards, Maxim Levitsky