Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp592191ybi; Sat, 15 Jun 2019 07:29:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqzD3irxweNg4Osqky4YjCxWd/yqQxV3eaE1Ww3ISMrPtW3ICrRavzy3/Hh7nfhY9dSPpNc6 X-Received: by 2002:a63:f510:: with SMTP id w16mr38096976pgh.0.1560608956881; Sat, 15 Jun 2019 07:29:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560608956; cv=none; d=google.com; s=arc-20160816; b=JWyexdiSVkvHZZYhV/IWDhcQtAnPm0X056sxsvvvAhMJJQyv5Vq6MvSPcXYi70Kkfj jSb7rHkvZBOiEt7s72aTUJMg7CN/5w4nk8xu3K1XLZL9mSCQ6ZhNzwcuMWOUHOMMlxEp RHR88t5N+i9BeeM9EKwZ5YqssGENxGy4u0/4pqsAoGIn6KfflczSytYO/GTXfAfYf42U BT7jJPKmc6x3irO//aIpzTXo7hnghlJSWwt+DGunXPxS9sv9eh5KJIVUuqTLVOmxUU80 Q2Ov2wc9el85jtHAKkRzBkU7jiXumPfwLY3rq4wP+xapIctOUo3f2ApnHnySYoPZaBPa V3JQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=QhBUca9l8uNPR6pas+aRrdYfwIq3RBG/VxFYNg2iqLw=; b=TshdUlFy1Ar7IZXr0V/vESIfbbSg5oyraQ13LqI0UKt6Y1pb1rsKUKrp9agREMPNeg QP7cfaA5rE0+JY/LUxp+Dd6MrBzeaYUoCu0ktUNgSX+kSmY7p/ounUFiK4eEFxNpV5L9 hxkDDNYzNC7pN77IQgsFeR/PMAJ++qoeOFqkdJ6Ixvm3//hK0nSr6DHLGJDKAP4j/RXN KsRWv2mrmRSoATcjrkkwYl5Qu+eE8FNWFzNMe1v6OyIMZRqDbq7BrLglVn8T79HxFyM1 VAyqf2N315o6zI3Mpp7MUOKpY8aGC9ghsMXKRTwppuzkZ6NsTjKFDxO84CN4aOrpSMl2 FG4Q== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d37si5082444plb.351.2019.06.15.07.29.00; Sat, 15 Jun 2019 07:29:16 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726847AbfFOO24 (ORCPT + 99 others); Sat, 15 Jun 2019 10:28:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56114 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725944AbfFOO24 (ORCPT ); Sat, 15 Jun 2019 10:28:56 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 3C37F308FBA0; Sat, 15 Jun 2019 14:28:56 +0000 (UTC) Received: from maximlenovopc.usersys.redhat.com (unknown [10.35.206.31]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3D3565D9E2; Sat, 15 Jun 2019 14:28:49 +0000 (UTC) Message-ID: <1d80a586342dfee0479db96a4457f7023b0260a9.camel@redhat.com> Subject: Re: [RFC PATCH 8/8] svm: Allow AVIC with in-kernel irqchip mode From: Maxim Levitsky To: "Suthikulpanit, Suravee" , Alex Williamson Cc: "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" , "x86@kernel.org" , "joro@8bytes.org" , "rkrcmar@redhat.com" , "pbonzini@redhat.com" , "tglx@linutronix.de" , "mingo@redhat.com" , "bp@alien8.de" , "hpa@zytor.com" , "jsteckli@amazon.de" , "sironi@amazon.de" , "wawei@amazon.de" Date: Sat, 15 Jun 2019 17:28:50 +0300 In-Reply-To: References: <20190204144128.9489-1-suravee.suthikulpanit@amd.com> <20190204144128.9489-9-suravee.suthikulpanit@amd.com> <20190205113404.5c5382e6@w520.home> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.43]); Sat, 15 Jun 2019 14:28:56 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2019-02-06 at 11:20 +0000, Suthikulpanit, Suravee wrote: > Alex, > > On 2/6/19 1:34 AM, Alex Williamson wrote: > > On Mon, 4 Feb 2019 14:42:32 +0000 > > "Suthikulpanit, Suravee" wrote: > > > > > Once the IRQ ack notifier for in-kernel PIT is no longer required > > > and run-time AVIC activate/deactivate is supported, we can remove > > > the kernel irqchip split mode requirement for AVIC. > > > > > > Hence, remove the check for irqchip split mode when enabling AVIC. > > > > Yay! Could we also at this point make avic enabled by default or are > > there remaining incompatibilities? Thanks, > > I'm looking into that next. I would need to ensure that enabling > AVIC would not cause issues with other features. > > Suravee Hi! Do you have any update on the state of this patch? I kind of stumbled on it accidently, while trying to understand why AVIC is only enabled in the split irqchip mode. Best regards, Maxim Levitsky